Protocols for Clinical Registry Extraction and Data Submission (CREDS) IG
1.0.0 - STU1 United States of America flag

Protocols for Clinical Registry Extraction and Data Submission (CREDS) IG, published by HL7 International / Clinical Interoperability Council. This is not an authorized publication; it is the continuous build for version 1.0.0. This version is based on the current content of https://github.com/HL7/fhir-registry-protocols-ig/ and changes regularly. See the Directory of published versions

ValueSet: Arterial Access Site (Experimental)

Official URL: http://hl7.org/fhir/us/registry-protocols/ValueSet/ArterialAccessSite Version: 1.0.0
Active as of 2023-11-14 Computable Name: ArterialAccessSite

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

Arterial Access Site

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

This value set includes codes based on the following rules:

 

Expansion

This value set contains 4 concepts

Expansion based on:

CodeSystemDisplay
  7657000http://snomed.info/sctFemoral artery
  17137000http://snomed.info/sctBrachial artery
  45631007http://snomed.info/sctRadial artery
  100013029http://hl7.org/fhir/us/registry-protocols/CodeSystem/ncdrOther

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