Moving a journal between EPJ systems

When an organization chooses to change their EPJ system, continuity is achieved by reconnecting the new EPJ to the existing SFM journal.
However, because EPJ vendors operate in separate SFM clusters with different endpoints, this is not a self‑service operation.
The transition requires coordination with Norsk helsenett (NHN) to ensure that the organization is moved from one SFM cluster to another and correctly connected to the existing SFM journal instance. All medication information (PLL, prescriptions, reactions, treatment history) remains in SFM and becomes available to the new EPJ once the cluster change and integration are completed. 
Note: NHN needs to be contacted on a 2 weeks notice, to be able to scedule the moving of the data from one cluster to another. 

When changing EPJ system, all data owned by the EPJ (outside SFM) must be transferred to the new EPJ to ensure correct interaction with the existing SFM instance. Master data such as Patients, Persons and Practitioners that are represented both in EPJ and in SFM must be migrated to the new EPJ so that the new EPJ can continue to act as the master system for these entities and interact correctly with the existing SFM journal. SFM data itself is not migrated and remains unchanged in the SFM instance.

When activating the organization in the new EPJ, the new EPJ is required to update epjinfo with system code, system name, and version.

Moving organzations from different SFM Journals into one joint SFM Journal is currently not supported. 

Søk i Utviklerportalen

Søket er fullført!