Introduction
Journalføringstjenesten (JFT) offers APIs for submitting and retrieving events to be added to the related patient's health records on a per-municipality level. The figure below shows the typical information flow.

- Events are recorded by welfare technology equipment and sent to a response center.
- The response center submits the event to JFT, and the event is added to JFT's event store.
- The municipality EHR system for health and care synchronizes with JFT, adding new events to the health records.
APIs
There are two APIs:
- WriteAPI: Endpoints for submitting new events and updating status.
- ReadAPI: Endpoints for searching and retrieving events.
Events are represented using the FHIR standard, version R4. OpenAPI documentation is available on the /swagger
endpoint in the Test environments.
Authentication with HelseID
Accessing the JFT APIs requires clients to be authenticated using HelseID and DPoP (Demonstrating Proof-of-Possession):
- Scope: Clients must request access to scope
nhn:jft/api. - Claim: Access token must include claim
helseid://claims/client/claims/orgnr_parent. - DPoP required: Only requests including DPoP tokens are accepted.
- Authorization header: Access token must be sent using the
DPoPprefix (i.e., notBearer). - DPoP-Proof: Requests must include a
DPoPheader with a signed proof generated by the client.
See HelseID documentation for implementation details.
Getting started
The following resources might help you to get started using JFT APIs:
- Step-by-step getting started guide
- Overview of how to use the APIs
- OpenAPI documentation
- HelseID documentation