Implementation Guide for fælles faglige instrumenter (FFInst)
1.0.0 - release
This page is part of the KLFFinst (v1.0.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Official URL: http://fhir.kl.dk/ffinst/ValueSet/SystolicBloodPressureSCTObservables | Version: 1.0.0 | |||
Active as of 2023-08-27 | Computable Name: SystolicBloodPressureSCTObservables |
SNOMED CT observables for systolic blood pressure
References
http://snomed.info/sct
Code | Display |
72313002 | Systolic arterial pressure |
400974009 | Standing systolic blood pressure (observable entity) |
399304008 | Systolic blood pressure on admission (observable entity) |
407556006 | Lying systolic blood pressure (observable entity) |
407554009 | Sitting systolic blood pressure (observable entity) |
271649006 | Systolic blood pressure |
This value set contains 6 concepts
Expansion based on:
Code | System | Display |
72313002 | http://snomed.info/sct | Systolic arterial pressure |
400974009 | http://snomed.info/sct | Standing systolic blood pressure (observable entity) |
399304008 | http://snomed.info/sct | Systolic blood pressure on admission (observable entity) |
407556006 | http://snomed.info/sct | Lying systolic blood pressure (observable entity) |
407554009 | http://snomed.info/sct | Sitting systolic blood pressure (observable entity) |
271649006 | http://snomed.info/sct | Systolic blood pressure |
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 |