Clinical Document Architecture V2.0.1
2.1.0-draft1 - 1st Draft

This page is part of the CDA: Clinical Document Architecture (v2.1.0-draft1: CDA 2.1 Draft) based on FHIR v5.0.0. . For a full list of available versions, see the Directory of published versions

Logical Model: Device (CDA Class)

Official URL: http://hl7.org/fhir/cda/StructureDefinition/Device Version: 2.1.0-draft1
Active as of 2023-01-16 Computable Name: CDAR2.Device

A ManufacturedMaterial used in an activity without being substantially changed through that activity. This includes durable (reusable) medical equipment as well as disposable equipment. The kind of device is identified by the code attribute inherited from Entity.

Usage:

  • This Logical Model Profile is not used by any profiles in this Implementation Guide

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraintsdoco
.. Device 1..1BaseBase for all types and resources
... classCode 1..1codeBinding: EntityClassDevice (required)
... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
... templateId 0..*II
... manufacturerModelName 0..1SC​Binding: http://terminology.hl7.org/ValueSet/v3-ManufacturerModelName (extensible)
... softwareName 0..1SC​Binding: http://terminology.hl7.org/ValueSet/v3-SoftwareName (extensible)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
Device.classCoderequiredEntityClassDevice
Device.determinerCoderequiredFixed Value: INSTANCE
Device.codeextensibleEntityCode
Device.manufacturerModelNameextensible​http://terminology.hl7.org/ValueSet/v3-ManufacturerModelName
Device.softwareNameextensible​http://terminology.hl7.org/ValueSet/v3-SoftwareName

Constraints

IdGradePath(s)DetailsRequirements
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())

This structure is derived from Base

Summary

Mandatory: 0 element (2 nested mandatory elements)
Fixed Value: 1 element

Differential View

This structure is derived from Base

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Device 1..1BaseBase for all types and resources
... classCode 1..1codeBinding: EntityClassDevice (required)
... determinerCode 1..1codeBinding: EntityDeterminer (required)
Fixed Value: INSTANCE
... templateId 0..*II
... manufacturerModelName 0..1SC​Binding: http://terminology.hl7.org/ValueSet/v3-ManufacturerModelName (extensible)
... softwareName 0..1SC​Binding: http://terminology.hl7.org/ValueSet/v3-SoftwareName (extensible)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
Device.classCoderequiredEntityClassDevice
Device.determinerCoderequiredFixed Value: INSTANCE
Device.codeextensibleEntityCode
Device.manufacturerModelNameextensible​http://terminology.hl7.org/ValueSet/v3-ManufacturerModelName
Device.softwareNameextensible​http://terminology.hl7.org/ValueSet/v3-SoftwareName

Constraints

IdGradePath(s)DetailsRequirements
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())

This structure is derived from Base

Summary

Mandatory: 0 element (2 nested mandatory elements)
Fixed Value: 1 element

 

Other representations of profile: CSV, Excel