Diagnostic Data Services

DDS-Message-Header-1

The Diagnostic Request resource describes the Message Header information.

NameCard.TypeDescription & Constraints
..MessageHeaderDomainResourceA resource that describes a message that is exchanged between systems

...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

...timestamp1..1InstantTime that the message was sent

...event1..1CodingCode for the event this message represents
Binding One of the message events defined as part of FHIR. (http://hl7.org/fhir/ValueSet/message-events)
Binding Strength Preferred

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

....system0..1UriIdentity of the terminology system

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

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

....display0..1StringRepresentation defined by the system

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

...response0..1BackboneElementIf this is a reply to prior message

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

....identifier1..1IdId of original message

....code1..1Codeok | transient-error | fatal-error
Binding The kind of response to a message (http://hl7.org/fhir/ValueSet/response-code)
Binding Strength Required

....details0..1Reference (OperationOutcome)Specific list of hints/warnings/errors

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

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

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

...source1..1BackboneElementMessage Source Application

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

....name0..1StringName of system

....software0..1StringName of software running the system

....version0..1StringVersion of software running

....contact0..1ContactPointHuman contact for problems

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

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

.....value0..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/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

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

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

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

....endpoint1..1UriActual message source address or id

...destination0..*BackboneElementMessage Destination Application(s)

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

....name0..1StringName of system

....target0..1Reference (Device)Particular delivery destination within the destination

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

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

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

....endpoint1..1UriActual destination address or id

...enterer0..1Reference (Practitioner)The source of the data entry

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

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

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

...author0..1Reference (Practitioner)The source of the decision

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

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

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

...receiver0..1Reference (Practitioner | Organization)Intended "real-world" recipient for the data

...responsible0..1Reference (Practitioner | Organization)Final responsibility for event

...reason0..1CodeableConceptCause of event
Binding Reason for event occurrence (http://hl7.org/fhir/ValueSet/message-reason-encounter)
Binding Strength Example

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

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

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

.....system0..1UriIdentity of the terminology system

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

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

.....display0..1StringRepresentation defined by the system

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

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

...data0..*Reference (Resource)The actual content of the message

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

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

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

Path Name Binding Strength ValueSet
.MessageHeader.language language Required http://tools.ietf.org/html/bcp47
.MessageHeader.event event Preferred http://hl7.org/fhir/ValueSet/message-events
.MessageHeader.response.code code Required http://hl7.org/fhir/ValueSet/response-code
.MessageHeader.source.contact.system system Required http://hl7.org/fhir/ValueSet/contact-point-system
.MessageHeader.source.contact.use use Required http://hl7.org/fhir/ValueSet/contact-point-use
.MessageHeader.reason reason Example http://hl7.org/fhir/ValueSet/message-reason-encounter

DDS-Message-Header-1

Examples Description XML File
DDS-Message-Header-1-Example-Report An example of the DDS Message Header