US Core Implementation Guide, published by HL7 International / Cross-Group Projects. This guide is not an authorized publication; it is the continuous build for version 9.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/US-Core/ and changes regularly. See the Directory of published versions
| Official URL: http://hl7.org.fhir/us/core/ValueSet/us-core-pmo-servicerequest-category | Version: 9.0.0-ballot | |||
| Standards status: Trial-use | Maturity Level: 3 | Computable Name: USCorePMOServiceRequestCategory | ||
| Other Identifiers: OID:2.16.840.1.113883.4.642.40.2.48.10 | ||||
Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License |
||||
The PMO ServiceRequest Category Value Set is used to indicate that the ServiceRequest is instantiated based on a Portable Medical Order (PMO) document.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Changes since version 8.0.0:
http://hl7.org/fhir/us/core/CodeSystem/us-core-category version 📦9.0.0-ballot| Code | Display | Definition |
| PMO | Portable Medical Order (PMO) | Portable Medical Order (PMO) category |
Expansion performed internally based on codesystem US Core Category v9.0.0-ballot (CodeSystem)
This value set contains 1 concepts
| System | Code | Display (en) | JSON | XML |
http://hl7.org/fhir/us/core/CodeSystem/us-core-category | PMO | Portable Medical Order (PMO) |
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 |