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

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

ValueSet: R5MedicationrequestCategoryForR3

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-medicationrequest-category-for-R3 Version: 0.1.0
Standards status: Trial-use Maturity Level: 1 Responsible: Pharmacy Computable Name: R5MedicationrequestCategoryForR3

This cross-version ValueSet represents content from http://terminology.hl7.org/ValueSet/medicationrequest-category|0.1.0 for use in FHIR STU3.

This value set is part of the cross-version definitions generated to enable use of the value set http://terminology.hl7.org/ValueSet/medicationrequest-category|0.1.0 as defined in FHIR R5 in FHIR STU3.

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

  • ConditionDefinition.medication.category as Example

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

  • http://terminology.hl7.org/ValueSet/medicationrequest-category|0.1.0
  • http://hl7.org/fhir/ValueSet/medicationrequest-category|4.3.0
  • http://hl7.org/fhir/ValueSet/medicationrequest-category|4.0.1

Note that all concepts are included in this cross-version definition because no concepts have compatible representations

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 (4). All concepts in the comparison are listed as identical. The source and target value sets have the same number of active concepts (4). FHIR ValueSet http://terminology.hl7.org/ValueSet/medicationrequest-category|0.1.0, defined in FHIR R5 does not have any mapping to FHIR STU3

References

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/medicationrequest-category version 📍0.1.0
    CodeDisplayDefinition
    communityCommunityIncludes requests for medications to be administered or consumed by the patient in their home (this would include long term care or nursing homes, hospices, etc.)
    dischargeDischargeIncludes requests for medications created when the patient is being released from a facility
    inpatientInpatientIncludes requests for medications to be administered or consumed in an inpatient or acute care setting
    outpatientOutpatientIncludes requests for medications to be administered or consumed in an outpatient setting (for example, Emergency Department, Outpatient Clinic, Outpatient Surgery, Doctor's office)

 

Expansion

This value set expansion contains 4 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://terminology.hl7.org/CodeSystem/medicationrequest-category0.1.0  communityCommunityIncludes requests for medications to be administered or consumed by the patient in their home (this would include long term care or nursing homes, hospices, etc.)
http://terminology.hl7.org/CodeSystem/medicationrequest-category0.1.0  dischargeDischargeIncludes requests for medications created when the patient is being released from a facility
http://terminology.hl7.org/CodeSystem/medicationrequest-category0.1.0  inpatientInpatientIncludes requests for medications to be administered or consumed in an inpatient or acute care setting
http://terminology.hl7.org/CodeSystem/medicationrequest-category0.1.0  outpatientOutpatientIncludes requests for medications to be administered or consumed in an outpatient setting (for example, Emergency Department, Outpatient Clinic, Outpatient Surgery, Doctor's office)

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