INTEROPen CareConnect Base STU3 Implementation Guide
3.0.0 - CI Build
INTEROPen CareConnect Base STU3 Implementation Guide - Local Development build (v3.0.0). See the Directory of published versions
Summary
| Defining URL: | https://fhir.hl7.org.uk/STU3/ValueSet/CareConnect-SpecimenType-1 |
| Version: | 3.0.0 |
| Name: | Care Connect Specimen Type |
| Status: | draft |
| Definition: | A code from the SNOMED Clinical Terminology UK coding system to record a specimen type. |
| Publisher: | INTEROpen |
| Copyright: | 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. |
| Source Resource: | XML / JSON / Turtle |
References
A code from the SNOMED Clinical Terminology UK coding system to record a specimen type.
Copyright Statement: 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.
This value set includes codes from the following code systems:
http://snomed.info/sct where constraint = (<105590001 |Substance (substance)| OR <49755003 |Morphologically abnormal structure (morphologic abnormality)| OR <260787004 |Physical object (physical object)|)
No Expansion for this valueset (not supported by Publication Tooling)
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 |