enforce trace context in http header

[martinsmock]

Add requirement to use the trace context as defined in W3C standard (https://www.w3.org/TR/trace-context/) for all transactions,

[oliveregger]

daniel will work on a proposal including also the mapping to soap:header

for FHIR transations we need to include it for each transaction where appropriate in

• referenced standards
• Message Semantics

[oliveregger]

indepent of daniel's work, we can integrate it

[qligier]

Do we describe now requirements to add the trace identifier to the audit events? It should be described here, and maybe in CH:ATC in the future too (?)

[oliveregger]

• we should mention it for sure how to add it to the FHIR AuditEvent resources in the IG
• for the DICOM AuditEvent Message this needs to be described in the Annex
• CH ATC should be in a future version also have that field enabled

[qligier]

BALP supports the X-Request-Id header, but not sure if it's the best mapping for traceparent too: https://chat.fhir.org/#narrow/stream/179223-ihe/topic/Specify.20tracing.20identifiers.20in.20AuditEvents.20.28BALP.29/near/419788189

https://profiles.ihe.net/ITI/BALP/content.html#35731-x-request-id-header

[qligier]

Issue raised in BALP: IHE/ITI.BasicAudit#94
See also: https://chat.fhir.org/#narrow/stream/179247-Security-and.20Privacy/topic/TraceID's
FHIR documentation with trace IDs: http://build.fhir.org/audit-event-example-create-traceID.html

[qligier]

Issue raised in BALP: IHE/ITI.BasicAudit#94

Create a PR for the two new headers