Test environments and SFM versions available
Below you will find an overview of SFM test environments and SFM versions available. The testenvironments are available for the vendors integrating with SFM. The vendors can create testorganizations, testusers and testpatients themselves to be used in testing with SFM fullversion or SFM Basis API. If you have newly started to integrate with SFM please see guidelines here: https://utviklerportal.nhn.no/informasjonstjenester/sentral-forskrivningsmodul The table is updated weekly. To order upgrade, see guidelines below the table.
Name of testenvironment |
Versions available |
Comments |
SFM Test5 |
SFM 4.8.0 SFM v4.10.0 SFM v4.11.1 SFM v4.12.0 |
SFM Basis API test environment |
SFM Test6 |
SFM v4.10.0 SFM v4.11.1 SFM v4.12.0 |
SFM Fullversion test environment |
Production |
SFM v4.8.0 SFM v4.10.0 SFM v4.11.1 |
Next version planned to production: . 4.12.0 first deploy on 27/3 |
SFM test environments in E-resept chain
Both SFM Basis API and SFM fullversion testenvironments are fully integrated with other testenvironments in the E-resept chain. Specifically, the SFM environments are integrated with:
· Reseptformidleren - RF-test2 environment
· Kjernejournal - KJ st1 environment
· SFM are also integrated with Helsepersonellregisteret (HPR) and HELFO testenvironments
Upgrade a testorganization
Vendors that want to test with a specific SFM version can order to upgrade a testrorganization to kundesenter@nhn.no. It is not possible to order to downgrade to a version. The following information need to be included for each testorganization to be upgraded:
· Name of testorganization
· Organizationnumber
· HERid
· Name of testenvironment
· Which version you want to test
· Please also remember to include SFM as a keyword in the subject of the email
Are you missing SFM test1 environment or SFM test2 environment?
Those test environments were using legacy platform while SFM test5 and test6 are on private cloud platform. Test1 and test2 were discontinued by 31st of January when all vendors had been moved to private cloud platform in production.