Extensions for Using Data Elements from FHIR STU3 in FHIR R5
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR STU3 in FHIR R5 - Downloaded Version null See the Directory of published versions

ValueSet: R3EncounterStatusForR5

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R3-encounter-status-for-R5 Version: 0.1.0
Standards status: Trial-use Maturity Level: 2 Responsible: Patient Administration Computable Name: R3EncounterStatusForR5

This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/encounter-status 3.0.2 for use in FHIR R5 that is appropriate for use but unavailable in http://hl7.org/fhir/ValueSet/encounter-status|5.0.0.

This value set is part of the cross-version definitions generated to enable use of the value set http://hl7.org/fhir/ValueSet/encounter-status|3.0.2 as defined in FHIR STU3 in FHIR R5.

The source value set is bound to the following FHIR STU3 elements:

  • Encounter.status as Required
  • Encounter.statusHistory.status as Required

Across FHIR versions, the value set has been mapped as:

  • http://hl7.org/fhir/ValueSet/encounter-status|3.0.2
  • http://hl7.org/fhir/ValueSet/encounter-status|4.0.1
  • http://hl7.org/fhir/ValueSet/encounter-status|4.3.0
  • http://hl7.org/fhir/ValueSet/encounter-status|5.0.0

The following concepts are not included in this cross-version definition because they have valid representations:

  • http://hl7.org/fhir/encounter-status#cancelled
  • http://hl7.org/fhir/encounter-status#entered-in-error
  • http://hl7.org/fhir/encounter-status#in-progress
  • http://hl7.org/fhir/encounter-status#onleave
  • http://hl7.org/fhir/encounter-status#planned

Following are the generation technical comments: All concepts in the comparison are listed as identical. The source and target value sets have the same number of active concepts (9). All concepts in the comparison are listed as identical. The source and target value sets have the same number of active concepts (9). One or more source concepts are either not mapped or broader than their targets, so the value set relationship is broadened. The source and target value sets have the same number of active concepts (9).

References

Logical Definition (CLD)

  • Include these codes as defined in http://hl7.org/fhir/encounter-status version 📍3.0.2
    CodeDisplayDefinition
    arrivedArrivedThe Patient is present for the encounter, however is not currently meeting with a practitioner.
    finishedFinishedThe Encounter has ended.
    triagedTriagedThe patient has been assessed for the priority of their treatment based on the severity of their condition.
    unknownUnknownThe encounter status is unknown. Note that "unknown" is a value of last resort and every attempt should be made to provide a meaningful value other than "unknown".

 

Expansion

This value set expansion contains 4 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://hl7.org/fhir/encounter-status3.0.2  arrivedArrivedThe Patient is present for the encounter, however is not currently meeting with a practitioner.
http://hl7.org/fhir/encounter-status3.0.2  finishedFinishedThe Encounter has ended.
http://hl7.org/fhir/encounter-status3.0.2  triagedTriagedThe patient has been assessed for the priority of their treatment based on the severity of their condition.
http://hl7.org/fhir/encounter-status3.0.2  unknownUnknownThe encounter status is unknown. Note that "unknown" is a value of last resort and every attempt should be made to provide a meaningful value other than "unknown".

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code