AU Base Implementation Guide
4.2.2-ci-build - CI Build
AU Base Implementation Guide, published by HL7 Australia. This guide is not an authorized publication; it is the continuous build for version 4.2.2-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7au/au-fhir-base/ and changes regularly. See the Directory of published versions
Official URL: http://terminology.hl7.org.au/ValueSet/accession-number-type | Version: 4.2.2-ci-build | |||
Standards status: Trial-use | Maturity Level: 1 | Computable Name: AccessionNumberType | ||
Other Identifiers: OID:2.16.840.1.113883.2.3.4.2.4.23 | ||||
Copyright/Legal: HL7 Australia© 2018+; Licensed Under Creative Commons No Rights Reserved. |
Identifier types that may be associated with an accession number in an Australian context.
References
Generated Narrative: ValueSet accession-number-type
http://terminology.hl7.org/CodeSystem/v2-0203
Code | Display | Definition |
ACSN | Accession ID | Accession Identifier |
LACSN | Laboratory Accession ID | A laboratory accession id is used in the laboratory domain. |
Generated Narrative: ValueSet
Expansion based on codesystem identifierType v4.0.0 (CodeSystem)
This value set contains 2 concepts
Code | System | Display | Definition |
ACSN | http://terminology.hl7.org/CodeSystem/v2-0203 | Accession ID | Accession Identifier |
LACSN | http://terminology.hl7.org/CodeSystem/v2-0203 | Laboratory Accession ID | A laboratory accession id is used in the laboratory domain. |
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 |