Canadian Baseline
1.2.0 - CI Build Canada flag

Canadian Baseline, published by HL7 Canada - FHIR Implementation Work Group. This guide is not an authorized publication; it is the continuous build for version 1.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7-Canada/ca-baseline/ and changes regularly. See the Directory of published versions

Resource Profile: Device Profile (Implantable)

Official URL: http://hl7.org/fhir/ca/baseline/StructureDefinition/profile-device Version: 1.2.0
Draft as of 2024-12-27 Computable Name: DeviceProfile

Proposed constraints on the Device resource for the minimal set of data to query and retrieve a patient's implantable device.

CA Baseline Device (Implantable) Profile

This profile is seeking broader community and implementer feedback on this profile.

The clinical substream review of this profile is paused until a Subject Matter Expert can be found who can speak to the use of implantable device data in Canada. Due to a lack of current Canadian FHIR implementation guides that surface a device profile - this profile has not undergone a Due Diligence Review and should be treated with caution until more community feedback can be acquired. Simplifier issue log for this profile.

This profile sets minimum expectations for the Device resource to record, search, and fetch UDI information associated with a patient's implantable device(s). It identifies which core elements SHALL be present in the resource when using this profile.

This profile defines core localization concepts for use in the Canadian context.

Mandatory Data Elements

All elements or attributes within the FHIR specification have cardinality as part of their definition - a minimum number of required appearances and a maximum number of allowable appearances.

Most elements in the FHIR specification have a minimum cardinality of 0, so most elements are not required and subsequently they may be missing from a resource when it is exchanged between systems.

Required elements in the Device (Implantable) profile:

  • A Unique Device Identifier (UDI) numeric or alphanumeric code (Device.deviceIdentifier):
    • either as the Human Readable Form (HRF) string representation of the barcode (Device.carrierHRF)
    • or the Automatic Identification and Data Capture representation (Device.carrierAIDC)
  • The type of the device (Device.type)
  • A patient (Device.patient)

Must Support Data Elements

Some elements are marked as Must Support. This means that implementations generating, receiving, or otherwise using resources with Must Support elements SHALL provide support for those elements in some meaningful way (see Must Support definition).

The following elements are marked as Must Support in the Device (Implantable) profile:

Must Support elements:

  • Unique Device Identifier (UDI) Barcode string
  • distinct identification string
  • device manufacturer
  • expiration date/time of the device
  • lot number of manufacture
  • serial number assigned by the manufacturer
  • name of the device
  • type of the device
  • version of the device
  • patient

Usage Note

The following are example usage scenarios for the implantable Device profile:

  • Query for a patient's implantable devices
  • Record or update a patient implantable device information

Usage:

Formal Views of Profile Content

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

NameFlagsCard.TypeDescription & Constraintsdoco
.. Device C 0..* Device Device Profile
dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources
dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
dom-5: If a resource is contained in another resource, it SHALL NOT have a security label
dom-6: A resource should have narrative for robust management
ca-device-1: Implantable medical devices that have UDI information MAY represent this information in either carrierAIDC or carrierHRF.
ca-device-2: For implantable medical devices that have UDI information, at least one of the Production Identifiers (UDI-PI) MAY be present.
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
ele-1: All FHIR elements must have a @value or children
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
... udiCarrier SΣ 1..1 BackboneElement Unique Device Identifier (UDI) Barcode string
ele-1: All FHIR elements must have a @value or children
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
.... deviceIdentifier SΣ 1..1 string Mandatory fixed portion of UDI
ele-1: All FHIR elements must have a @value or children
.... carrierAIDC SΣ 0..1 base64Binary UDI Machine Readable Barcode String
ele-1: All FHIR elements must have a @value or children
.... carrierHRF SΣ 0..1 string UDI Human Readable Barcode String
ele-1: All FHIR elements must have a @value or children
... distinctIdentifier S 0..1 string The distinct identification string
ele-1: All FHIR elements must have a @value or children
... manufacturer S 0..1 string Name of device manufacturer
ele-1: All FHIR elements must have a @value or children
... expirationDate S 0..1 dateTime Date and time of expiry of this device (if applicable)
ele-1: All FHIR elements must have a @value or children
... lotNumber S 0..1 string Lot number of manufacture
ele-1: All FHIR elements must have a @value or children
... serialNumber S 0..1 string Serial number assigned by the manufacturer
ele-1: All FHIR elements must have a @value or children
... deviceName S 0..* BackboneElement The name of the device as given by the manufacturer
ele-1: All FHIR elements must have a @value or children
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
.... name 1..1 string The name of the device
ele-1: All FHIR elements must have a @value or children
.... type 1..1 code udi-label-name | user-friendly-name | patient-reported-name | manufacturer-name | model-name | other
Binding: DeviceNameType (required): The type of name the device is referred by.


ele-1: All FHIR elements must have a @value or children
... type S 1..1 CodeableConcept The kind or type of device
Binding: FHIR Device Types (extensible): Codes to identify medical devices


ele-1: All FHIR elements must have a @value or children
... version S 0..* BackboneElement The actual design of the device or software version running on the device
ele-1: All FHIR elements must have a @value or children
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
ele-1: All FHIR elements must have a @value or children
ext-1: Must have either extensions or value[x], not both
.... value 1..1 string The version text
ele-1: All FHIR elements must have a @value or children
... patient 1..1 Reference(Patient Profile) Patient to whom Device is affixed
ele-1: All FHIR elements must have a @value or children
... parent 0..1 Reference(Device Profile (Implantable)) The parent device
ele-1: All FHIR elements must have a @value or children

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
Device.statusrequiredFHIRDeviceStatus
http://hl7.org/fhir/ValueSet/device-status|4.0.1
from the FHIR Standard
Device.deviceName.typerequiredDeviceNameType
http://hl7.org/fhir/ValueSet/device-nametype|4.0.1
from the FHIR Standard
Device.typeextensibleFHIRDeviceTypes
http://terminology.hl7.org/ValueSet/device-kind

Constraints

IdGradePath(s)DetailsRequirements
ca-device-1warningDeviceImplantable medical devices that have UDI information MAY represent this information in either carrierAIDC or carrierHRF.
: udiCarrier.empty() or (udiCarrier.carrierAIDC.exists() or udiCarrier.carrierHRF.exists())
ca-device-2warningDeviceFor implantable medical devices that have UDI information, at least one of the Production Identifiers (UDI-PI) MAY be present.
: udiCarrier.empty() or (manufactureDate.exists() or expirationDate.exists() or lotNumber.exists() or serialNumber.exists() or distinctIdentifier.exists())
dom-2errorDeviceIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorDeviceIf the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
: contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorDeviceIf a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5errorDeviceIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceDeviceA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

 

Other representations of profile: CSV, Excel, Schematron