Connectathon 11 Snapshot

This page is part of the FHIR Specification (v1.2.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

U.S. Data Access Framework (DAF) Encounter profile vs QICore-Encounter

Messages

A series of messages from the comparison algorithm. Errors indicate that solutions cannot be interoperable across both implementation guides (or that there are structural flaws in the definition of at least one).

PathMessage
Errors Detected
(None)
Notes about differences (e.g. definitions)
Encounter.extensionElements differ in definition for short:
"Additional Content defined by implementations"
"Extension"
Encounter.extensionElements differ in definition for definition:
"May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension."
"An Extension"
Encounter.statusElements differ in definition for short:
"planned | in-progress | onleave | finished | cancelled"
"planned | arrived | in-progress | onleave | finished | cancelled"
Encounter.statusElements differ in definition for definition:
"planned | in-progress | onleave | finished | cancelled."
"planned | arrived | in-progress | onleave | finished | cancelled."
Encounter.typeElements differ in definition for binding.description:
"Encounter type Value set to describe the type of encounter."
"Encounter Type Value set to describe the type of encounter"
Encounter.priorityExample/preferred bindings differ at Encounter.priority using binding from QICore-Encounter
Encounter.priorityElements differ in definition for binding.description:
"Indicates the urgency of the encounter."
"The priority of the encounter (e.g., Urgent, Normal, etc.)"
Encounter.patientElements differ in definition for short:
"Patient present at encounter"
"The patient present at the encounter"
Encounter.patientElements differ in definition for definition:
"Patient present at encounter."
"The patient present at the encounter."
Encounter.reasonElements differ in definition for binding.description:
"Encounter Diagnoses Value set to describe the specific encounter code."
"Encounter Reason Value Set to describe reason for encounter"
Encounter.hospitalization.dischargeDispositionElements differ in definition for binding.description:
"Value set to describe kind of location or category of discharge."
"Discharge Disposition"

Intersection

The intersection of the 2 constraint statements. This is what resource authors (either client or server) would need to conform to produce content valid against both implementation guides.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter 0..*EncounterAn interaction during which services are provided to the patient
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S ∑0..*IdentifierIdentifier(s) by which this encounter is known
... status ?! S∑1..1codeleft: planned | in-progress | onleave | finished | cancelled; right: planned | arrived | in-progress | onleave | finished | cancelled
Binding: EncounterState (required)
... statusHistory 0..*BackboneElementList of past encounter statuses
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... status 1..1codeplanned | arrived | in-progress | onleave | finished | cancelled
Binding: EncounterState (required)
.... period 1..1PeriodThe time that the episode was in the specified status
... class S ∑0..1codeinpatient | outpatient | ambulatory | emergency +
Binding: EncounterClass (required)
... type S ∑0..1CodeableConceptSpecific type of encounter
Binding: DAF Encounter Type (preferred)
... priority 0..1CodeableConceptIndicates the urgency of the encounter
Binding: SNOMED CT Priorities Codes (preferred)
... patient S ∑1..1Reference(DAF-Patient)left: Patient present at encounter; right: The patient present at the encounter
... episodeOfCare ∑0..*Reference(EpisodeOfCare)Episode(s) of care that this encounter should be recorded against
... incomingReferral 0..*Reference(QICore-ReferralRequest)The ReferralRequest that initiated this encounter
... participant S ∑0..*BackboneElementList of participants involved in the encounter
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... type S ∑0..*CodeableConceptRole of participant in encounter
Binding: ParticipantType (extensible)
.... period 0..1PeriodPeriod of time during the encounter participant was present
.... individual S ∑0..1Reference(DAF-Pract | DAF-RelatedPerson)Persons involved in the encounter other than the patient
... appointment ∑0..1Reference(Appointment)The appointment that scheduled this encounter
... period S0..1PeriodThe start and end time of the encounter
... length S0..1DurationQuantity of time the encounter lasted (less time absent)
... reason S ∑0..1CodeableConceptReason the encounter takes place (code)
Binding: DAF Encounter Diagnoses (extensible)
... indication 0..*Reference(Condition | Procedure)Reason the encounter takes place (resource)
... hospitalization S0..1BackboneElementDetails about the admission to a healthcare service
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... preAdmissionIdentifier 0..1IdentifierPre-admission identifier
.... origin 0..1Reference(QICore-Location)The location from which the patient came before admission
.... admitSource S0..1CodeableConceptFrom where patient was admitted (physician referral, transfer)
Binding: AdmitSource (preferred)
.... admittingDiagnosis 0..*Reference(Condition)The admitting diagnosis as reported by admitting practitioner
.... reAdmission S0..1CodeableConceptThe type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission
Binding: (unbound) (example)
.... dietPreference 0..*CodeableConceptDiet preferences reported by the patient
Binding: Diet (example)
.... specialCourtesy 0..*CodeableConceptSpecial courtesies (VIP, board member)
Binding: SpecialCourtesy (preferred)
.... specialArrangement 0..*CodeableConceptWheelchair, translator, stretcher, etc.
Binding: SpecialArrangements (preferred)
.... destination 0..1Reference(QICore-Location)Location to which the patient is discharged
.... dischargeDisposition S0..1CodeableConceptCategory or kind of location after discharge
Binding: DAF Encounter Discharge Disposition (extensible)
.... dischargeDiagnosis S0..*Reference(Condition)The final diagnosis given a patient before release from the hospital after all testing, surgery, and workup are complete
... location S0..1BackboneElementList of locations where the patient has been
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... location S1..1Reference(DAF-Location)Location the encounter takes place
.... status 0..1codeplanned | active | reserved | completed
Binding: EncounterLocationStatus (required)
.... period 0..1PeriodTime period during which the patient was present at the location
... serviceProvider S0..1Reference(QICore-Organization)The custodian organization of this Encounter record
... partOf 0..1Reference(QICore-Encounter)Another Encounter this encounter is part of

doco Documentation for this format

Union

The union of the 2 constraint statements. This is what resource authors (either client or server) would need to be able to handle to accept content valid against either implementation guides.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter 0..*EncounterAn interaction during which services are provided to the patient
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... encounter-reasonCancelled 0..1CodeableConceptExtension
URL: http://hl7.org/fhir/StructureDefinition/encounter-reasonCancelled
Binding: Reasons for canceled or refused encounter codes (example)
... encounter-relatedCondition 0..*Reference(Condition)Extension
URL: http://hl7.org/fhir/StructureDefinition/encounter-relatedCondition
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S ∑0..*IdentifierIdentifier(s) by which this encounter is known
... status ?! S∑1..1codeleft: planned | in-progress | onleave | finished | cancelled; right: planned | arrived | in-progress | onleave | finished | cancelled
Binding: EncounterState (required)
... statusHistory 0..*BackboneElementList of past encounter statuses
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... status 1..1codeplanned | arrived | in-progress | onleave | finished | cancelled
Binding: EncounterState (required)
.... period 1..1PeriodThe time that the episode was in the specified status
... class S ∑0..1codeinpatient | outpatient | ambulatory | emergency +
Binding: EncounterClass (required)
... type S ∑0..*CodeableConceptSpecific type of encounter
Binding: DAF Encounter Type (preferred)
... priority 0..1CodeableConceptIndicates the urgency of the encounter
Binding: ???? (preferred)
... patient S ∑0..1Reference(#1)left: Patient present at encounter; right: The patient present at the encounter
... episodeOfCare ∑0..*Reference(EpisodeOfCare)Episode(s) of care that this encounter should be recorded against
... incomingReferral 0..*Reference(ReferralRequest)The ReferralRequest that initiated this encounter
... participant S ∑0..*BackboneElementList of participants involved in the encounter
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... type S ∑0..*CodeableConceptRole of participant in encounter
Binding: ParticipantType (extensible)
.... period 0..1PeriodPeriod of time during the encounter participant was present
.... individual S ∑0..1Reference(#3 | #5)Persons involved in the encounter other than the patient
... appointment ∑0..1Reference(Appointment)The appointment that scheduled this encounter
... period S0..1PeriodThe start and end time of the encounter
... length S0..1DurationQuantity of time the encounter lasted (less time absent)
... reason S ∑0..*CodeableConceptReason the encounter takes place (code)
Binding: DAF Encounter Diagnoses (extensible)
... indication 0..*Reference(Condition | Procedure)Reason the encounter takes place (resource)
... hospitalization S0..1BackboneElementDetails about the admission to a healthcare service
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... preAdmissionIdentifier 0..1IdentifierPre-admission identifier
.... origin 0..1Reference(Location)The location from which the patient came before admission
.... admitSource S0..1CodeableConceptFrom where patient was admitted (physician referral, transfer)
Binding: AdmitSource (preferred)
.... admittingDiagnosis 0..*Reference(Condition)The admitting diagnosis as reported by admitting practitioner
.... reAdmission S0..1CodeableConceptThe type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission
Binding: (unbound) (example)
.... dietPreference 0..*CodeableConceptDiet preferences reported by the patient
Binding: Diet (example)
.... specialCourtesy 0..*CodeableConceptSpecial courtesies (VIP, board member)
Binding: SpecialCourtesy (preferred)
.... specialArrangement 0..*CodeableConceptWheelchair, translator, stretcher, etc.
Binding: SpecialArrangements (preferred)
.... destination 0..1Reference(Location)Location to which the patient is discharged
.... dischargeDisposition S0..1CodeableConceptCategory or kind of location after discharge
Binding: ???? (extensible)
.... dischargeDiagnosis S0..*Reference(Condition)The final diagnosis given a patient before release from the hospital after all testing, surgery, and workup are complete
... location S0..*BackboneElementList of locations where the patient has been
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... location S1..1Reference(#6)Location the encounter takes place
.... status 0..1codeplanned | active | reserved | completed
Binding: EncounterLocationStatus (required)
.... period 0..1PeriodTime period during which the patient was present at the location
... serviceProvider S0..1Reference(Organization)The custodian organization of this Encounter record
... partOf 0..1Reference(Encounter)Another Encounter this encounter is part of

doco Documentation for this format