Event Lifecycle
This page shows an example on how the JFT API can be used to report a new event, and follow it throughout its lifecycle.
- Acme Inc.'s software system EvRep is used to report events.
- HealthRecords Corp.'s software system HRec is the EHR system.
Note
Some of the endpoints are not implemented yet. See Roadmap and the OpenApi docs for latest status.
Report event
A Bundle event is reported by Acme's EvRep SW using JFT's WriteAPI.
The header nhn-source-system is optional, but Acme use it to identify the system
which generated the event.
JFT registers the event at timestamp 2026-01-01 00:01 and allocates resourceId="abc"
for the event.
Check status (1)
After reporting the event, Acme checks the status of the event resource using the
Status endpoint and the resourceId.
The response indicates that the event has been successfully registered in JFT.
Read events
HealthRecords reads new events using the search endpoint and the _lastUpdated parameter.
The ReadApi logs the read event and returns the affected event resource in a searchset.
The value specified by Acme in the nhn-source-system header is included in a meta extension
field in the returned resource.
Acknowledge journaling of event
HRec creates a journal note for the event, and sends an acknowledge message to update the event status in JFT.
Check status (2)
Acme verifies that the event they reported has been successfully journaled. No further action is required.
