R6 Ballot (3rd Draft) FHIR CI-Build

This page is part of the FHIR Specification v6.0.0-ballot3: Release 6 Ballot (3rd Draft) (see Ballot Notes ). The current version is 5.0.0 . For a full list Continuous Integration Build of available versions, see FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

8.17 8.16 Resource DeviceAssociation - Content

Responsible Owner: Orders and Observations icon Work Group Maturity Level : 0   Draft Security Category : Patient Compartments : Device , Group , Patient , Practitioner , RelatedPerson

A record of association or dissociation of a device with a patient. subject (e.g. patient) and/or operator.

Device Association records the relationship between a device and a subject and/or operator. The relationsip may be as the owner, patient, operator or cusodian of the device. The scope covers all devices including, but not limited to: implantables (which previously was documented as the .association in the Device resource), implantables, wheelchairs, RTLS, personal health and point of care devices, diagnostic, imaging and durable medical equipment. This resource is intended to apply to any delivery environment and discipline where a device association is useful to record.

The subjects may include:

  • Patient - the following are often associated with a specific patient: implantables, prosthetics, activity trackers, mobility assistance, care monitoring, etc.
  • Group - some devices may be associated with a family group or treatment group. For example a weight scale or blood pressure cuff.
  • Practitioner - a device that is associated with the practitioner: pager, alert monitor, cell phone, laptop/tablet
  • Device - a device may be associated with another device when it is independent of the focal device. Note: this is different than the containment tree with parent element in the Device resource. For example a RFID tag used to track the location of a wheelchair.
  • RelatedPerson - a device that is associated with another person related to the patient. For example, an alerting device given to a spouse while their partner is in surgery.
  • DeviceAssociation (this resource) - To clarify when tracking the lifecycle and traceability of a device, including assignment or dissociation with a patient, practitioner, location, or another device.
  • Device - This resource contains the association (incluuding history) between a The device and a subject, eliminating that is, e.g., used, placed in or on, or owned by the need for subject referenced in the Device resource to contain that history of associations which might allow unintended exposure of patient information. DeviceAssociation.
  • DeviceUsage icon and when documenting a patient’s use of a device — typically clinical history or their ongoing reliance on the device.
  • Procedure - Both Procedure and DeviceUsage can comprehend association (not necessarily when the related dissociation) of a device with is involved in a subject. They are intended to be used from the patient of process perspective. For tracking the act of implanting clinical action, such as implantation, removal, or using the device, Procedure may be used; For updating the patient's information about the usage adjustment, where details of a device, DeviceUsage may that intervention need to be used; For tracking the different events along the lifecycle of the same Device, DeviceAssociation is appropriate recorded.

These are not exclusive, i.e. when associating a device with a patient, the it is possible to capture the patient's clinical information with a DeviceUsage resource, include the device in a Procedure resources may be used together — for reporting, and keep the Device's traceability information with example, a DeviceAssociation resource. procedure may establish or end an association, while DeviceUsage captures continued patient use.

To track changes in settings, the Observation resource can be used, where Observation.subject references the Device that the settings apply to. If, e.g., the patient that the Device is associated with needs to be identified, then the DeviceAssociation where DeviceAssociation.period includes the Observation.effective[x] would have that patient in DeviceAssociation.subject. DeviceAssociation.subject .

No references for this Resource.

Structure

implanted | explanted 0..* The individual performing the action enabled by
Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . DeviceAssociation Σ D DomainResource A record of association or dissociation of a device with a patient subject (e.g. patient) and/or operator

Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . identifier Σ 0..* Identifier Instance identifier

. . . device Σ 1..1 Reference ( Device ) Reference to the devices device that is being associated with the patient or group
. . . relationship Σ 0..* CodeableConcept Describes the relationship between the device and subject
Binding: DeviceAssociation Relationship Codes ( Extensible )

. . . statusReason Σ 0..* CodeableConcept The reasons given for the current association status
Binding: DeviceAssociation Status Reason Codes ( Required Extensible )

. . . associationStatus Σ 0..1 CodeableConcept State of the device’s association
Binding: DeviceAssociation Association Status ( Preferred )
... subject Σ 0..1 Reference ( Patient BiologicallyDerivedProduct | CareTeam | Device | Group | Location | Medication | NutritionProduct | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | Device Specimen | Substance ) The individual, group of individuals or device entity(ies) that the device is on or associated with
. . bodyStructure . focus Σ 0..1 Reference ( BodyStructure ) Current anatomical location of the device in/on subject period BiologicallyDerivedProduct | CareTeam Σ | Device 0..1 Period | Group Begin and end dates and times for the device association operation | Location | Medication Σ | NutritionProduct 0..* BackboneElement | Organization The details about the device when it is in use to describe its operation status | Patient | Practitioner Σ | PractitionerRole 1..1 CodeableConcept | RelatedPerson Device operational condition Binding: FHIR Device Association Operation Status | Specimen ( Example | Substance ) The target of the association
. . . operator bodyStructure Σ 0..1 Reference ( Patient | Practitioner | RelatedPerson BodyStructure ) Current anatomical location of the device in/on subject
. . . period Σ 0..1 Period Begin and end dates and times for the device's operation device association

doco Documentation for this format icon

See the Extensions for this resource

UML Diagram ( Legend )

DeviceAssociation ( DomainResource ) Instance identifier identifier : Identifier [0..*] Reference to the devices device that is being associated with the patient or group device : Reference [1..1] « Device » Describes the relationship between the device and subject relationship : CodeableConcept [0..*] « A coded concept specifying the type of association. (Strength=Extensible) DeviceAssociationCodes + » Indicates the state of the Device association status : CodeableConcept code [1..1] « A coded concept specifying the state of the device association. (Strength=Required) DeviceAssociationCodes ! » The reasons given for the current association status statusReason : CodeableConcept [0..*] « null (Strength=Required) (Strength=Extensible) DeviceAssociationCodes ! + » State of the device’s association (e.g., implanted, attached, on, off, standby, defective) associationStatus : CodeableConcept [0..1] « States that characterize the device’s association/operational state with respect to the subject. (Strength=Preferred) DeviceAssociationAssociationS... ? » The individual, group of individuals or device that the device is on or associated with subject : Reference [0..1] « Patient BiologicallyDerivedProduct | CareTeam | Device | Group | Organization Location | Practitioner Medication | NutritionProduct | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | Device Specimen » | Current anatomical location of the device in/on subject bodyStructure : Reference [0..1] « BodyStructure Substance » Begin and end dates and times The entity for which the device is being used, benefitting from the device, or which the device is being operated upon, which is usually distinct from the association subject, such as an operator or similar period focus : Period Reference [0..1] « BiologicallyDerivedProduct | CareTeam | Operation Device | Group | Location | Medication | NutritionProduct | Organization | Device operational condition corresponding to the association status Patient : CodeableConcept | Practitioner [1..1] « | PractitionerRole | RelatedPerson | Specimen | A coded concept specifying the status of the association operation. (Strength=Example) FHIRDeviceAssociationOperatio... Substance ?? » The individual performing the action enabled by Current anatomical location of the device in/on subject operator bodyStructure : Reference [0..*] [0..1] « Patient | Practitioner | RelatedPerson BodyStructure » Begin and end dates and times for the device's operation device association period : Period [0..1] The details about the device when it is in use to describe its operation operation [0..*]

XML Template

<

<DeviceAssociation xmlns="http://hl7.org/fhir"> doco

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Instance identifier --></identifier>
 <</device>

 <device><!-- 1..1 Reference(Device) Reference to the device that is being associated --></device>

 <relationship><!-- 0..* CodeableConcept Describes the relationship between the device and subject --></relationship>
 <</status>

 <status value="[code]"/><!-- 1..1 active | inactive | entered-in-error | unknown -->

 <statusReason><!-- 0..* CodeableConcept The reasons given for the current association status --></statusReason>
 <|
   </subject>

 <associationStatus><!-- 0..1 CodeableConcept State of the device’s association --></associationStatus>
 <subject><!-- 0..1 Reference(BiologicallyDerivedProduct|CareTeam|Device|Group|
   Location|Medication|NutritionProduct|Organization|Patient|Practitioner|
   PractitionerRole|RelatedPerson|Specimen|Substance) The entity(ies) that the device is on or associated with --></subject>

 <focus><!-- 0..1 Reference(BiologicallyDerivedProduct|CareTeam|Device|Group|
   Location|Medication|NutritionProduct|Organization|Patient|Practitioner|
   PractitionerRole|RelatedPerson|Specimen|Substance) The target of the association --></focus>
 <bodyStructure><!-- 0..1 Reference(BodyStructure) Current anatomical location of the device in/on subject --></bodyStructure>
 <period><!-- 0..1 Period Begin and end dates and times for the device association --></period>
 <
  <</status>
  <</operator>
  <</period>
 </operation>

</DeviceAssociation>

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:;

[ a fhir:DeviceAssociation;

  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from 
  # from 

  # from Resource: fhir:id, fhir:meta, fhir:implicitRules, and fhir:language
  # from DomainResource: fhir:text, fhir:contained, fhir:extension, and fhir:modifierExtension

  fhir:identifier  ( [ Identifier ] ... ) ; # 0..* Instance identifier
  fhir:

  fhir:device [ Reference(Device) ] ; # 1..1 Reference to the device that is being associated

  fhir:relationship  ( [ CodeableConcept ] ... ) ; # 0..* Describes the relationship between the device and subject
  fhir:

  fhir:status [ code ] ; # 1..1 active | inactive | entered-in-error | unknown

  fhir:statusReason  ( [ CodeableConcept ] ... ) ; # 0..* The reasons given for the current association status
  fhir:

  fhir:associationStatus [ CodeableConcept ] ; # 0..1 State of the device’s association
  fhir:subject [ Reference(BiologicallyDerivedProduct|CareTeam|Device|Group|Location|Medication|
  NutritionProduct|Organization|Patient|Practitioner|PractitionerRole|
  RelatedPerson|Specimen|Substance) ] ; # 0..1 The entity(ies) that the device is on or associated with

  fhir:focus [ Reference(BiologicallyDerivedProduct|CareTeam|Device|Group|Location|Medication|
  NutritionProduct|Organization|Patient|Practitioner|PractitionerRole|
  RelatedPerson|Specimen|Substance) ] ; # 0..1 The target of the association
  fhir:bodyStructure [ Reference(BodyStructure) ] ; # 0..1 Current anatomical location of the device in/on subject
  fhir:period [ Period ] ; # 0..1 Begin and end dates and times for the device association
  fhir:
    fhir:
    fhir:
    fhir:
  ] ... ) ;

]

Changes from both R4 and R4B

This resource did not exist in Release R4

See the Full Difference for further information

This analysis is available for R4 as XML or JSON and for R4B as XML or JSON .

Structure

implanted | explanted 0..* The individual performing the action enabled by
Name Flags Card. Type Description & Constraints      Filter: Filters doco
. . DeviceAssociation Σ D DomainResource A record of association or dissociation of a device with a patient subject (e.g. patient) and/or operator

Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . identifier Σ 0..* Identifier Instance identifier

. . . device Σ 1..1 Reference ( Device ) Reference to the devices device that is being associated with the patient or group
. . . relationship Σ 0..* CodeableConcept Describes the relationship between the device and subject
Binding: DeviceAssociation Relationship Codes ( Extensible )

. . . statusReason Σ 0..* CodeableConcept The reasons given for the current association status
Binding: DeviceAssociation Status Reason Codes ( Required Extensible )

. . . associationStatus Σ 0..1 CodeableConcept State of the device’s association
Binding: DeviceAssociation Association Status ( Preferred )
... subject Σ 0..1 Reference ( Patient BiologicallyDerivedProduct | CareTeam | Device | Group | Location | Medication | NutritionProduct | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | Device Specimen | Substance ) The individual, group of individuals or device entity(ies) that the device is on or associated with
. . bodyStructure . focus Σ 0..1 Reference ( BodyStructure ) Current anatomical location of the device in/on subject period BiologicallyDerivedProduct | CareTeam Σ | Device 0..1 Period | Group Begin and end dates and times for the device association operation | Location | Medication Σ | NutritionProduct 0..* BackboneElement | Organization The details about the device when it is in use to describe its operation status | Patient | Practitioner Σ | PractitionerRole 1..1 CodeableConcept | RelatedPerson Device operational condition Binding: FHIR Device Association Operation Status | Specimen ( Example | Substance ) The target of the association
. . . operator bodyStructure Σ 0..1 Reference ( Patient | Practitioner | RelatedPerson BodyStructure ) Current anatomical location of the device in/on subject
. . . period Σ 0..1 Period Begin and end dates and times for the device's operation device association

doco Documentation for this format icon

See the Extensions for this resource

UML Diagram ( Legend )

DeviceAssociation ( DomainResource ) Instance identifier identifier : Identifier [0..*] Reference to the devices device that is being associated with the patient or group device : Reference [1..1] « Device » Describes the relationship between the device and subject relationship : CodeableConcept [0..*] « A coded concept specifying the type of association. (Strength=Extensible) DeviceAssociationCodes + » Indicates the state of the Device association status : CodeableConcept code [1..1] « A coded concept specifying the state of the device association. (Strength=Required) DeviceAssociationCodes ! » The reasons given for the current association status statusReason : CodeableConcept [0..*] « null (Strength=Required) (Strength=Extensible) DeviceAssociationCodes ! + » State of the device’s association (e.g., implanted, attached, on, off, standby, defective) associationStatus : CodeableConcept [0..1] « States that characterize the device’s association/operational state with respect to the subject. (Strength=Preferred) DeviceAssociationAssociationS... ? » The individual, group of individuals or device that the device is on or associated with subject : Reference [0..1] « Patient BiologicallyDerivedProduct | CareTeam | Device | Group | Organization Location | Practitioner Medication | NutritionProduct | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | Device Specimen » | Current anatomical location of the device in/on subject bodyStructure : Reference [0..1] « BodyStructure Substance » Begin and end dates and times The entity for which the device is being used, benefitting from the device, or which the device is being operated upon, which is usually distinct from the association subject, such as an operator or similar period focus : Period Reference [0..1] « BiologicallyDerivedProduct | CareTeam | Operation Device | Group | Location | Medication | NutritionProduct | Organization | Device operational condition corresponding to the association status Patient : CodeableConcept | Practitioner [1..1] « | PractitionerRole | RelatedPerson | Specimen | A coded concept specifying the status of the association operation. (Strength=Example) FHIRDeviceAssociationOperatio... Substance ?? » The individual performing the action enabled by Current anatomical location of the device in/on subject operator bodyStructure : Reference [0..*] [0..1] « Patient | Practitioner | RelatedPerson BodyStructure » Begin and end dates and times for the device's operation device association period : Period [0..1] The details about the device when it is in use to describe its operation operation [0..*]

XML Template

<

<DeviceAssociation xmlns="http://hl7.org/fhir"> doco

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Instance identifier --></identifier>
 <</device>

 <device><!-- 1..1 Reference(Device) Reference to the device that is being associated --></device>

 <relationship><!-- 0..* CodeableConcept Describes the relationship between the device and subject --></relationship>
 <</status>

 <status value="[code]"/><!-- 1..1 active | inactive | entered-in-error | unknown -->

 <statusReason><!-- 0..* CodeableConcept The reasons given for the current association status --></statusReason>
 <|
   </subject>

 <associationStatus><!-- 0..1 CodeableConcept State of the device’s association --></associationStatus>
 <subject><!-- 0..1 Reference(BiologicallyDerivedProduct|CareTeam|Device|Group|
   Location|Medication|NutritionProduct|Organization|Patient|Practitioner|
   PractitionerRole|RelatedPerson|Specimen|Substance) The entity(ies) that the device is on or associated with --></subject>

 <focus><!-- 0..1 Reference(BiologicallyDerivedProduct|CareTeam|Device|Group|
   Location|Medication|NutritionProduct|Organization|Patient|Practitioner|
   PractitionerRole|RelatedPerson|Specimen|Substance) The target of the association --></focus>
 <bodyStructure><!-- 0..1 Reference(BodyStructure) Current anatomical location of the device in/on subject --></bodyStructure>
 <period><!-- 0..1 Period Begin and end dates and times for the device association --></period>
 <
  <</status>
  <</operator>
  <</period>
 </operation>

</DeviceAssociation>

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:;

[ a fhir:DeviceAssociation;

  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from 
  # from 

  # from Resource: fhir:id, fhir:meta, fhir:implicitRules, and fhir:language
  # from DomainResource: fhir:text, fhir:contained, fhir:extension, and fhir:modifierExtension

  fhir:identifier  ( [ Identifier ] ... ) ; # 0..* Instance identifier
  fhir:

  fhir:device [ Reference(Device) ] ; # 1..1 Reference to the device that is being associated

  fhir:relationship  ( [ CodeableConcept ] ... ) ; # 0..* Describes the relationship between the device and subject
  fhir:

  fhir:status [ code ] ; # 1..1 active | inactive | entered-in-error | unknown

  fhir:statusReason  ( [ CodeableConcept ] ... ) ; # 0..* The reasons given for the current association status
  fhir:

  fhir:associationStatus [ CodeableConcept ] ; # 0..1 State of the device’s association
  fhir:subject [ Reference(BiologicallyDerivedProduct|CareTeam|Device|Group|Location|Medication|
  NutritionProduct|Organization|Patient|Practitioner|PractitionerRole|
  RelatedPerson|Specimen|Substance) ] ; # 0..1 The entity(ies) that the device is on or associated with

  fhir:focus [ Reference(BiologicallyDerivedProduct|CareTeam|Device|Group|Location|Medication|
  NutritionProduct|Organization|Patient|Practitioner|PractitionerRole|
  RelatedPerson|Specimen|Substance) ] ; # 0..1 The target of the association
  fhir:bodyStructure [ Reference(BodyStructure) ] ; # 0..1 Current anatomical location of the device in/on subject
  fhir:period [ Period ] ; # 0..1 Begin and end dates and times for the device association
  fhir:
    fhir:
    fhir:
    fhir:
  ] ... ) ;

]

Changes from both R4 and R4B

This resource did not exist in Release R4

See the Full Difference for further information

This analysis is available for R4 as XML or JSON and for R4B as XML or JSON .

 

Additional definitions: Master Definition XML + JSON , XML Schema / Schematron + JSON Schema , ShEx (for Turtle ) + see the extensions , the spreadsheet version & the dependency analysis

DeviceAssociation.operation.status
Path ValueSet Type Documentation
DeviceAssociation.relationship DeviceAssociationCodes (a valid code from DeviceAssociation Relationship Codes ) Extensible

DeviceAssociation Relationship Codes

DeviceAssociation.status DeviceAssociationCodes (a valid code from DeviceAssociation Status Codes ) Required

DeviceAssociation Status Codes

DeviceAssociation.statusReason DeviceAssociationCodes (a valid code from DeviceAssociation Status Reason Codes ) Required Extensible

DeviceAssociation Status Reason Codes

DeviceAssociation.associationStatus FHIRDeviceAssociationOperationStatus DeviceAssociationAssociationStatus (a valid code from DeviceAssociation Association Status Codes ) Example Preferred

The status for Codes that describe the device state of a device’s association operation. (e.g., implanted, attached, on, off, standby, defective).

Search parameters for this resource. See also the full list of search parameters for this resource , and check the Extensions registry for search parameters on extensions related to this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

Name Type Description Expression In Common
date TU date Search for associations at or within specific times DeviceAssociation.period
device TU reference Search for products that match this code DeviceAssociation.device
( Device )
focus reference The focus of an association. DeviceAssociation.focus
( Group , Organization , CareTeam , BiologicallyDerivedProduct , Device , Patient , PractitionerRole , RelatedPerson , Practitioner , Specimen , NutritionProduct , Medication , Substance , Location )
identifier TU token The identifier of the device association DeviceAssociation.identifier
operator TU patient reference The identity of a operator for whom to list associations patient associated with the device DeviceAssociation.operation.operator DeviceAssociation.subject.where(resolve() is Patient)
( Practitioner , Patient , RelatedPerson )
61 Resources
relationship TU token Search for specific device association relationships DeviceAssociation.relationship
status TU token The status of the device associations DeviceAssociation.status
subject TU reference The identity of a patient the individual(s) or entity for whom to list associations DeviceAssociation.subject
( Practitioner , Group , Organization , CareTeam , BiologicallyDerivedProduct , Device , Patient , PractitionerRole , RelatedPerson , Practitioner , Specimen , NutritionProduct , Medication , Substance , Location )