HL7 Terminology
2.0.0 - Publication
This page is part of the HL7 Terminology (v2.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions
Summary
Defining URL: | http://terminology.hl7.org/ValueSet/ex-diagnosisrelatedgroup |
Version: | 0.2.0 |
Name: | ExampleDiagnosisRelatedGroupCodes |
Title: | Example Diagnosis Related Group Codes |
Status: | Draft as of 2020-02-24T12:41:39+11:00 (Standards Status: Draft) |
Definition: | This value set includes example Diagnosis Related Group codes. |
Publisher: | Financial Management |
Committee: | Financial Management |
Copyright: | This is an example set. |
Maturity: | 1 |
OID: | 2.16.840.1.113883.4.642.3.588 (for OID based terminology systems) |
Source Resource: | XML / JSON / Turtle |
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/ex-diagnosisrelatedgroup
This value set contains 4 concepts
Expansion based on Example Diagnosis Related Group Codes v0.1.0 (CodeSystem)
All codes from system http://terminology.hl7.org/CodeSystem/ex-diagnosisrelatedgroup
Code | Display | Definition |
100 | Normal Vaginal Delivery | Normal Vaginal Delivery. |
101 | Appendectomy - uncomplicated | Appendectomy without rupture or other complications. |
300 | Tooth abscess | Emergency department treatment of a tooth abscess. |
400 | Head trauma - concussion | Head trauma - concussion. |
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 |
Source | 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 |
History
Date | Action | Author | Custodian | Comment |
2020-10-14 | revise | Grahame Grieve | Vocabulary WG | Reset Version after migration to UTG |
2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |