This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions 
Responsible Owner: Orders and Observations Work Group | Draft | Security Category: Patient | Compartments: Device, Group, Patient, Practitioner, RelatedPerson |
Detailed Descriptions for the elements in the DeviceAssociation resource.
| DeviceAssociation | |
| Element Id | DeviceAssociation |
| Definition | A record of a relationship between a device and the entity to which it is directly associated. |
| Short Display | A record of association of a device with a subject |
| Cardinality | 0..* |
| Type | DomainResource |
| Summary | true |
| DeviceAssociation.identifier | |
| Element Id | DeviceAssociation.identifier |
| Definition | Instance identifier. |
| Short Display | Instance identifier |
| Note | This is a business identifier, not a resource identifier (see discussion) |
| Cardinality | 0..* |
| Type | Identifier |
| Summary | true |
| DeviceAssociation.device | |
| Element Id | DeviceAssociation.device |
| Definition | Reference to the device that is being associated. |
| Short Display | Reference to the device that is being associated |
| Cardinality | 1..1 |
| Type | Reference(Device) |
| Summary | true |
| DeviceAssociation.relationship | |
| Element Id | DeviceAssociation.relationship |
| Definition | Describes the relationship between the device and subject. |
| Short Display | Describes the relationship between the device and subject |
| Cardinality | 0..* |
| Terminology Binding | DeviceAssociation Relationship Codes (Example) |
| Type | CodeableConcept |
| Summary | true |
| DeviceAssociation.status | |
| Element Id | DeviceAssociation.status |
| Definition | Indicates the state of the Device association. |
| Short Display | active | inactive | entered-in-error | unknown |
| Cardinality | 1..1 |
| Terminology Binding | DeviceAssociation Status Codes (Required) |
| Type | code |
| Summary | true |
| DeviceAssociation.statusReason | |
| Element Id | DeviceAssociation.statusReason |
| Definition | Administrative or record-management reason for the current DeviceAssociation record status. |
| Short Display | Administrative or record-management reason for the record status |
| Cardinality | 0..* |
| Terminology Binding | DeviceAssociation Status Reason Codes (Preferred) |
| Type | CodeableConcept |
| Summary | true |
| DeviceAssociation.associationStatus | |
| Element Id | DeviceAssociation.associationStatus |
| Definition | State of the relationship between the device and subject. |
| Short Display | State of the device association relationship |
| Cardinality | 0..1 |
| Terminology Binding | DeviceAssociation Association Status (Preferred) |
| Type | CodeableConcept |
| Summary | true |
| DeviceAssociation.subject | |
| Element Id | DeviceAssociation.subject |
| Definition | The entity that is the direct target of the device association. This may be a person, role, organization, location, group, care team, or another device. The subject is not necessarily the patient or ultimate beneficiary of the association. The nature of the association is described by relationship. |
| Short Display | The direct target of the device association |
| Cardinality | 0..1 |
| Type | Reference(BiologicallyDerivedProduct | CareTeam | Device | Group | Location | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| Summary | true |
| Comments | When the device is directly assigned to, used by, carried by, worn by, monitored by, or otherwise associated with a caregiver, guardian, family member, or other non-patient individual, a RelatedPerson may be used as the subject. This is appropriate when the RelatedPerson is the direct target of the association, rather than merely participating in the care context of another individual. For example, an alert receiver assigned to a parent on behalf of a child may be represented with the parent as the subject of the DeviceAssociation. |
| DeviceAssociation.focus | |
| Element Id | DeviceAssociation.focus |
| Definition | One or more care, organizational, or operational contexts for which the device association exists or is interpreted. Use focus when the subject alone does not fully explain the purpose or context of the association, such as when a device is associated with one entity but supports, monitors, protects, or benefits another. Do not use focus to identify performers, installers, maintainers, or operators merely because they performed an activity involving the device. When different focuses require different relationships, periods, statuses, or traceability, use separate DeviceAssociation instances. |
| Short Display | Context for interpreting the device association |
| Cardinality | 0..* |
| Type | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| Summary | true |
| DeviceAssociation.bodyStructure | |
| Element Id | DeviceAssociation.bodyStructure |
| Definition | Current anatomical location(s) of the device in/on subject. |
| Short Display | Current anatomical location(s) of the device in/on subject |
| Cardinality | 0..* |
| Terminology Binding | SNOMED CT Body Structures (Example) |
| Type | CodeableReference(BodyStructure) |
| Summary | true |
| DeviceAssociation.period | |
| Element Id | DeviceAssociation.period |
| Definition | Begin and end dates and times for the device association. |
| Short Display | Begin and end dates and times for the device association |
| Cardinality | 0..1 |
| Type | Period |
| Summary | true |