KIP Infracstructure
0.2.1 - release
This page is part of the KIP Infrastructure (v0.2.1: Release) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 2.9.0. For a full list of available versions, see the Directory of published versions
| Official URL: https://kip.rkkp.dk/fhir/ValueSet/Rytme1Obs | Version: 0.2.1 | |||
| Active as of 2022-06-29 | Computable Name: Rytme1Obs | |||
Første observerede hjerterytme
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Generated Narrative: ValueSet Rytme1Obs
https://kip.rkkp.dk/fhir/CodeSystem/Rytme1Obs| Code | Display | Definition |
| vf | VF | VF |
| pulslos_vt | Pulsløs VT | Pulsløs VT |
| pea | PEA | PEA |
| asystoli | Asystoli | Asystoli |
| ingen_man | Ingen manuel rytmeanalyse | Ingen manuel rytmeanalyse |
| pulsgiv | Pulsgivende | Pulsgivende |
ValueSet
Expansion performed internally based on codesystem Hjerterytme - første obs v0.2.1 (CodeSystem)
This value set contains 6 concepts
| Code | System | Display (en-US) | Definition |
| vf | https://kip.rkkp.dk/fhir/CodeSystem/Rytme1Obs | VF | |
| pulslos_vt | https://kip.rkkp.dk/fhir/CodeSystem/Rytme1Obs | Pulsløs VT | |
| pea | https://kip.rkkp.dk/fhir/CodeSystem/Rytme1Obs | PEA | |
| asystoli | https://kip.rkkp.dk/fhir/CodeSystem/Rytme1Obs | Asystoli | |
| ingen_man | https://kip.rkkp.dk/fhir/CodeSystem/Rytme1Obs | Ingen manuel rytmeanalyse | |
| pulsgiv | https://kip.rkkp.dk/fhir/CodeSystem/Rytme1Obs | Pulsgivende |
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 |