| Excerpt |
|---|
This page describes the types of event messages that are published to destinations (topic/queue) on the message broker for the eHealth Infrastructure |
The eHealth Infrastructure publishes numerous events as part of the business processes carried out on the Platform.
This pagedescribes page describes the types of event messages that are published to destinations (topic/queue) on the message broker for the eHealth Infrastructure. Each message consists of a JSON body and additionally some message properties.
...
Simple Events are published at a CRUD resource level. This means that these can be generated as a side-effect of a business event. In the example below a ProcedureRequest ServiceRequest has been created as a side-effect of applying a CarePlan to a Patient’s EpisodeOfCare.
| Code Block | ||
|---|---|---|
| ||
{
"messageType": "EHealthSimpleEvent",
"messageVersion": "1.0",
"eventType": "created",
"resourceReference": "http://careplan.inttest.ehealth.sundhed.dk/fhir/ProcedureRequestServiceRequest/68",
"resourceVersion": "1"
}
Message properties:
{
date = Fri, 27 Sep 2019 09:37:59 GMT
server = istio-envoy
expires = Thu, 01 Jan 1970 00:00:00 GMT
x-envoy-upstream-service-time = 1
messageversion = 1.0
transfer-encoding = chunked
messagetype = EHealthSimpleEvent
x-frame-options = SAMEORIGIN
destination = topic://ehealth-procedurerequestservicerequest
patientreference = http://patient.inttest.ehealth.sundhed.dk/fhir/Patient/10907
resourcereference = http://careplan.inttest.ehealth.sundhed.dk/fhir/ProcedureRequestServiceRequest/68
pragma = no-cache
resourceprofile = ehealth-procedurerequestservicerequest
content-type = text/plain; charset=ISO-8859-1
eventtype = created
id = ID:careplan-6b7f84d69d-sdpkp-39827-1569566074696-1:2:66:3:1
cache-control = no-cache, no-store, must-revalidate
messageclass = com.systematic.ehealth.event.event.EHealthSimpleEvent
} |