Vital Records Death Reporting (VRDR) FHIR Implementation Guide, published by HL7 International / Public Health. This guide is not an authorized publication; it is the continuous build for version 3.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/vrdr/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/us/vrdr/ValueSet/vrdr-certifier-types-vs | Version: 3.0.0 | |||
Active as of 2024-09-16 | Computable Name: CertifierTypesVS | |||
Other Identifiers: OID:2.16.840.1.113883.4.642.40.10.48.3 | ||||
Copyright/Legal: This value set includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement |
Certifier Types Value Set
Mapping to IJE codes here.
References
Changes since version true:
Generated Narrative: ValueSet vrdr-certifier-types-vs
This value set includes codes based on the following rules:
http://snomed.info/sct
Code | Display |
455381000124109 | Death certification by medical examiner or coroner (procedure) |
434641000124105 | Death certification and verification by physician (procedure) |
434651000124107 | Death certification by physician (procedure) |
http://terminology.hl7.org/CodeSystem/v3-NullFlavor
Code | Display | Definition |
OTH | Other (Specify) | **Description:**The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system). **Usage Notes**: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to \*any\* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE. |
Generated Narrative: ValueSet
Expansion based on:
This value set contains 4 concepts
Code | System | Display | Definition |
455381000124109 | http://snomed.info/sct | Death certification by medical examiner or coroner (procedure) | |
434641000124105 | http://snomed.info/sct | Death certification and verification by physician (procedure) | |
434651000124107 | http://snomed.info/sct | Death certification by physician | |
OTH | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | Other (Specify) | **Description:**The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system). Usage Notes: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE. |
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 |