There are some important differences between test and production you as a developer should keep in mind:

  • In test, NHN will give you access to a pre-configured environment if you want. You will be able to access this by using test tools provided by NHN. Use this only for initial investigation, and set up your own instance as soon as possible.

  • First of all, you will need to set up a simulated customer. You will need a registry in Bedriftsregisteret to simulate a healthcare unit, and make sure it is available in Kjernejournal as well as Reseptformidleren. A relevant business category (næringskode) should be selected.

  • If you are new to e-resept, you will need a pre-registered Systemcode granted from Godkjenningsprosessen e-resept. The code will be registered in Reseptformidleren test, and will be propagated to production on approval.

  • You will need one or a set of Practitioners, with adequate professions registered in Helsepersonellregisteret (HPR). To be able to use e-resept, ensure that at least one of them has prescription rights. The SFM team will provide practitioners.

  • Similarly, you will need a set of patients. We strongly advise not to use the old test patients from the KITH list. The SFM team provides test persons based on your needs.

  • HelseID: Your system must be defined in HelseID selvbetjening as a Client system (Klientsystem), consuming the SFM API. If you choose to provide multi tenancy, this client defines everything in HelseID, including definition of Tenants. If you choose single tenancy, separate clients will be defined for each customer.

  • In test the SFM team may support a "delete everything", useful in initial testing, especially if migration goes wrong.

Build good support into your system

Using test tools and direct access to APIs is valuable in initial testing. Reproduction of errors by the SFM team requires precise information on endpoints, payloads and timestamps that are generally available in test. Do consider building good functions for this into your application from the start, as this proves valuable for production support later. Including, but not limited to:

  • log of payload for request and response, header information including access token and timestamp for operations on Organization and Practitioner

  • possibility to turn on similar logging also for Patient by a configuration switch

Søk i Utviklerportalen

Søket er fullført!