CardX - Cardiac Implantable Electronic Devices
1.0.0-ballot - STU 1 - Ballot International flag

CardX - Cardiac Implantable Electronic Devices, published by HL7 International / Clinical Interoperability Council. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/CardX-CIED/ and changes regularly. See the Directory of published versions

ValueSet: CIED Monitor Types

Official URL: http://hl7.org/fhir/uv/cardx-cied/ValueSet/cied-monitor-types-vs Version: 1.0.0-ballot
Standards status: Trial-use Maturity Level: 2 Computable Name: CIEDMonitorTypesVS

The type of CIED monitor

References

Logical Definition (CLD)

 

Expansion

Expansion performed internally based on codesystem CIED Connectivity Status Values v1.0.0-ballot (CodeSystem)

This value set contains 3 concepts

CodeSystemDisplay (en-US)Definition
  bedside-devicehttp://hl7.org/fhir/uv/cardx-cied/CodeSystem/CIEDconnectivityStandalone device, not intended to provide monitoring while on the go.Standalone device, not intended to provide monitoring while on the go.
  mobile-monitorhttp://hl7.org/fhir/uv/cardx-cied/CodeSystem/CIEDconnectivityApp based monitor.App based monitor.
  portable-devicehttp://hl7.org/fhir/uv/cardx-cied/CodeSystem/CIEDconnectivityStandalone device, with battery capacity to provide monitoring while on the go.Standalone device, with battery capacity to provide monitoring while on the go.

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