ITK - Document Reference

ITK-Device-1

This resource identifies an instance of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device.

NameCard.TypeDescription & Constraints
..DeviceDeviceAn instance of a manufactured item that is used in the provision of healthcare

...id0..1IdLogical id of this artifact

...meta0..1MetaMetadata about the resource

...implicitRules0..1UriA set of rules under which this content was created

...language0..1CodeLanguage of the resource content
Binding A human language. (http://tools.ietf.org/html/bcp47)
Binding Strength Required

...text0..1NarrativeText summary of the resource, for human interpretation

...contained0..*ResourceContained, inline Resources

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

....id0..1Idxml:id (or equivalent in JSON)

....value1..1StringSystem or medical device identifier

....assigner0..1Reference (CareConnect-Organization-1)Organization that issued id (may be just text)

.....id0..1Idxml:id (or equivalent in JSON)

.....reference1..1StringRelative 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. (https://fhir.nhs.uk/ValueSet/DeviceType-1)
Binding Strength Preferred

....id0..1Idxml:id (or equivalent in JSON)

....coding0..*CodingA reference to a code defined by a terminology system

.....id0..1Idxml:id (or equivalent in JSON)

.....system1..1UriIdentity of the terminology system

.....code1..1CodeSymbol in syntax defined by the system

.....display1..1StringRepresentation defined by the system

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

...note0..*AnnotationDevice notes and comments

....id0..1Idxml:id (or equivalent in JSON)

....author[x]0..1Reference (CareConnect-Practitioner-1 | ITK-RelatedPerson-1)Individual 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/DSTU2/valueset-devicestatus.html)
Binding Strength Required

...manufacturer0..1StringName of device manufacturer

...model0..1StringModel id assigned by the manufacturer

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

...manufactureDate0..1DateTimeManufacture date

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

...lotNumber0..1StringLot number of manufacture

...owner0..1Reference (CareConnect-Organization-1)Organization responsible for device

....id0..1Idxml:id (or equivalent in JSON)

....reference1..1StringRelative URL reference

....display0..1StringNarrative text for the resource

...location0..1Reference (CareConnect-Location-1)Where the resource is found

....id0..1Idxml:id (or equivalent in JSON)

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

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

...patient0..1Reference (CareConnect-Patient-1)If the resource is affixed to a person

....id0..1Idxml:id (or equivalent in JSON)

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

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

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

....id0..1Idxml:id (or equivalent in JSON)

....system1..1Codephone | fax | email | pager | other
Binding Telecommunications form for contact point (http://hl7.org/fhir/DSTU2/valueset-contact-point-system.html)
Binding Strength Required

....value1..1StringThe actual contact point details

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

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

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

.....id0..1Idxml:id (or equivalent in JSON)

.....start0..1DateTimeStarting time with inclusive boundary

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

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