Messaging (workflow)

As a consequence of evolving technology and practical considerations, there are three alternatives for establishing messaging between actors in the health net. All of them are subject to conformity to standardization, governed by "Helsedirektoratet" (The Norwegian Directorate of Health)

EDI (SMTP/ebXml)

This is the oldest and still the prevalent way of handling message. It is entirely based on specifications from The Norwegian Directorate of Health's specifications for the entire messaging process and actual message content. Email (smtp) is the carrier, EbXml is the wrapper/addressing format, and the payload is the actual XML standard message.

General information and specifications can be found  on the NHN web and The Norwegian Directorate of Health's web.

RabbitMQ Servicebus

The service bus is a high availability queue system based on RabbitMQ. It is used for negotiating traffic between Helsenorge and various actors in the health net.

You can read the specs on Helsenorge's documentation space. Some information and documentation on how to use this messaging system can also be found on the NHN web.

EDI 2.0

EDI 2.0 is a relatively new addition to the messaging alternatives. It is designed to make messaging simpler and faster. The central component is our own messaging server that is fully compatible with the old solution (SMTP/ebXml), but keeps all the complexities away from end-user systems (EHRs and other healthcare-related systems).

EDI 2.0 implements standard REST endpoints (Json/OpenAPI), authenticated with HelseID.

EDI 2.0 is currently in production, and the user base is steadily growing. All technical specs can be found in utviklerportalen (you are already here).