CH EPR mHealth (R4)
3.0.0 - DSTU3
This page is part of the CH EPR mHealth (R4) (v3.0.0: DSTU3) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
For all transaction described in this implementation guide, the HTTP traceparent
header is required. This header
is defined in the W3C Trace Context Recommendation.
The header value is made of four parts separated by dashes: the version, trace-id, parent-id and trace-flags. For example:
GET /request HTTP/1.1
traceparent: 00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-00
00
.00
.Each actor shall support the traceparent
header. Grouped actors shall use the same trace-id value to correlate
IHE transactions.
The traceparent
header value of the generated message SHALL be added to the generated Audit Event: for the client,
the header value of the request; for the responder, the header value of the response.
It is described as an AuditEvent.entity
, with the system
https://profiles.ihe.net/ITI/BALP/CodeSystem/BasicAuditEntityType#Traceparent
, as demonstrated below.
{
"resourceType" : "AuditEvent",
/* Rest of the AuditEvent */
"entity" : [
{
"what" : {
"identifier" : {
"value" : "00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-00"
}
},
"type" : {
"system" : "https://profiles.ihe.net/ITI/BALP/CodeSystem/BasicAuditEntityType",
"code" : "Traceparent"
}
}
]
}