Diagnostic Data Services

DDS-Report-Device-1-0

A medication is a substance that is packaged and used as an administered medication. The medication resource uses the substance resource to represent the actual ingredients of a medication.

Follow this link to view examples for DDS-Report-Device-1-0: Examples
NameCard.TypeDescription & Constraints
..DeviceDeviceAn instance of a manufactured te that is used in the provision of healthcare

...identifier0..*IdentifierInstance id from manufacturer, owner, and others

....use0..1Codeusual | official | temp | secondary (If known)
Binding: Identifies the purpose for this identifier, if known . (http://hl7.org/fhir/ValueSet/identifier-use)
Binding Strength: Required

....type0..1CodeableConceptDescription of identifier
Binding: A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. (http://hl7.org/fhir/ValueSet/identifier-type)
Binding Strength: Extensible

.....coding0..*CodingCode defined by a terminology system

......system1..1UriIdentity of the terminology system
Example Value: http://hl7.org/fhir/ValueSet/identifier-type

......version0..1StringVersion of the system - if relevant

......code1..1CodeSymbol in syntax defined by the system
Example Value: SNO

......display1..1StringRepresentation defined by the system
Example Value: Serial Number

......userSelected0..1BooleanIf this coding was chosen directly by the user

.....text0..1StringPlain text representation of the concept

....system1..1UriThe namespace for the identifier
Example Value: http://acme.com/devices/pacemakers/octane/serial

....value1..1StringThe value that is unique
Example Value: 1234-5678-90AB-CDEF

....period0..1PeriodTime period when id is/was valid for use

.....start1..1DateTimeStarting time with inclusive boundary

.....end0..1DateTimeEnd time with inclusive boundary, if not ongoing

....assigner0..1OrganizationOrganization that issued id (may be just text)

.....reference1..1StringRelative, internal or absolute URL reference

.....display0..1StringText alternative for the resource

...type1..1CodeableConceptWhat kind of device this is
Binding: Defines the nature of the device and the kind of functionality/services/behavior that may be expected from it. (http://acme.com/devices)
Binding Strength: Preferred

....coding0..1CodingCode defined by a terminology system

.....system1..1UriIdentity of the terminology system
Example Value: http://acme.com/devices

.....version0..1StringVersion of the system - if relevant

.....code1..1CodeSymbol in syntax defined by the system
Example Value: octane2014

.....display1..1StringRepresentation defined by the system
Example Value: Performance pace maker for high octane patients

.....userSelected0..1BooleanIf this coding was chosen directly by the user

....text0..1StringPlain text representation of the concept

...note0..*AnnotationDevice notes and comments

....author[x]0..1Practitioner, Patient, RelatedPerson, StringIndividual responsible for the annotation

....time0..1DateTimeWhen the annotation was made

....text1..1StringThe annotation - text content

...status0..1Codeavailable | not-available | entered-in-error
Binding: The availability status of the device. (http://hl7.org/fhir/ValueSet/devicestatus)
Binding Strength: Required

...manufacturer0..1StringName of device manufacturer
Example Value: Acme Devices, Inc

...model0..1StringModel id assigned by the manufacturer
Example Value: PM/Octane 2014

...version0..1StringVersion number (i.e. software)

...manufactureDate0..1DateTimeManufacture date

...expiry0..1DateTimeDate and time of expiry of this device (if applicable)

...udi0..1StringFDA mandated Unique Device Identifier

...lotNumber0..1StringLot number of manufacture
Example Value: 1234-5678

...owner0..1OrganizationOrganization responsible for device

....reference1..1StringRelative, internal or absolute URL reference

....display0..1StringText alternative for the resource

...location0..1LocationWhere the resource is found

....reference1..1StringRelative, internal or absolute URL reference

....display0..1StringText alternative for the resource

...patient0..1PatientIf the resource is affixed to a person

....reference1..1StringRelative URL reference

....display0..1StringText alternative for the resource

...contact0..*ContactPointDetails for human/organization for support

....system1..1Codephone | fax | email | pager | other
Binding: Telecommunications form for contact point (http://hl7.org/fhir/ValueSet/contact-point-system)
Binding Strength: Required
Example Value: phone

....value1..1StringThe actual contact point details
Example Value: ext 4352

....use0..1Codehome | work | temp | old | mobile - purpose of this contact point
Binding: Use of contact point (http://hl7.org/fhir/ValueSet/contact-point-use)
Binding Strength: Required

....rank0..1PositiveIntSpecify preferred order of use (1 = highest)

....period0..1PeriodTime period when the contact point was/is in use

.....start1..1DateTimeStarting time with inclusive boundary

.....end0..1DateTimeEnd time with inclusive boundary, if not ongoing

...url0..1UriNetwork address to contact device