This page is part of the FHIRcast (v2.1.0-ballot: STU3 Ballot 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions
This section presents the template to use for defining new events.
eventMaturity | 0 - Draft |
Describe when this event occurs in a workflow. Describe how the context fields relate to one another. Event creators SHOULD include as much detail and clarity as possible to minimize any ambiguity or confusion amongst implementors.
Define context values that are provided when this event occurs, and indicate whether they must be provided, and the FHIR query used to generate the resource.
Key | Optionality | FHIR operation to generate context | Description |
---|---|---|---|
example |
REQUIRED | FHIRresource/{id}?_elements=identifer |
Describe the context value |
encounter |
OPTIONAL | Encounter/{id} |
Describe the context value |
{
"timestamp": "2018-01-08T01:37:05.14",
"id": "q9v3jubddqt63n1",
"event": {
"hub.topic": "fdb2f928-5546-4f52-87a0-0648e9ded065",
"hub.event": "patient-open",
"context": [
{
"key": "key-from-above",
"resource": {
"resourceType": "resource-type-from-above"
}
},
{
"key": "encounter",
"resource": {
"resourceType": "Encounter"
}
}
]
}
}
Changes made to an event’s definition SHALL be documented in a change log to ensure event consumers can track what has been changed over the life of an event. The change log SHALL contain the following elements:
For example:
Version | Description |
---|---|
1.1 | Added new context FHIR object |
1.0.1 | Clarified workflow description |
1.0 | Initial Release |