Publisert - 04.11.2026

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.

JFT information flow

  1. Events are recorded by welfare technology equipment and sent to a response center.
  2. The response center submits the event to JFT, and the event is added to JFT's event store.
  3. 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):

  1. Scope: Clients must request access to scope nhn:jft/api.
  2. Claim: Access token must include claim helseid://claims/client/claims/orgnr_parent.
  3. DPoP required: Only requests including DPoP tokens are accepted.
  4. Authorization header: Access token must be sent using the DPoP prefix (i.e., not Bearer).
  5. DPoP-Proof: Requests must include a DPoP header 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

Søk i Utviklerportalen

Søket er fullført!