Getting started as an EHR/EPJ developer on integrating the SFM Basis API

This documentation presents the information you will need to integrate your EHR system to SFM Basis API. However, there are technologies involved that might be confusing if SFM is the first system you meet them:

• HelseID: OAuth tokens used for single sign-on, including the HelseID self service and multi tenancy solutions
• FHIR: Fast Healthcare interoperable resources, an international platform specification for healthcare interoperability

You will need basic knowledge to these topics to be able to understand the documentation for SFM. As an example, we do rely on you to understand that you need to create a JSON or XML payload and POST this to SFM when we document "Create Organization".

If you are NOT familiar with FHIR, a good place to start is: FHIR Release 4B

For more details, please also be sure you understand:

• RESTful API
• Search
• And as SFM uses Profiling and Extensions; Extensibility
• General operations on Organization, Person and Practitioner are following the RESTful guide above, but the major operations retreiving and submitting a patients medication information are based on FHIR operations: Exended operations

For HelseID, there is a lot of documentation elsewhere in this portal.

Selecting between SFM Full and SFM Basis

I you haven't discussed this already, you probably shall dig into SFM Full. SFM Basis is dedicated for major vendors, aiming for making a full blown medication module, or simply integrating existing module to norwegian e-prescription.

SFM Full gives you access to a medication module made for the norwegian e-prescription chain.