SFM Basis API Implementation Guide

Task

In the SFM Basis context, the national systems Reseptformidleren and Kjernejournal may be polled for a list of patients having changes:

Reseptformidleren keeps track of changes for patients belonging to a single multidose responsibility registration (Practitioner+Organisation)

Kjernejournal exposes a general service to poll for changes on a list of patients.

Basis GET /Task only supports code=8 and code=10 as search parameters. A code=10 search may return tasks with Task.code 10 and/or Task.code 17 in the bundle (for example when an M15 answer is present). Other task types in sfm-task-types are not additional Basis search options.

TASK retrieval for RF/Multidose

GET [base]/Task?code=8&owner=<HPR>&_lastUpdated=gt<dateTime>

Organisation is implicit given claims in HelseID token, owner is optional and overrides personal identity in token. This operation may be performed without personal identity in token.

Note the following: Code=8 is from codesystem: sfm-task-types and is "Endring på multidosepasient" Returns a list with one task for each multidosepatient registered in the given combination (organisation /practitioner) having changes in Reseptformidleren since the _lastUpdated time.

TASK retrieval for Kjernejournal

GET [base]/Task?code=10&_lastUpdated=gt<dateTime>&patientNiN=a,b,c...

Organisation is implicit given claims in HelseID token. patientNiN contains a list of patients to check for changes against Kjernejournal This operation may be performed without personal identity in token.

Note the following: Code=10 is from codesystem: sfm-task-types and is "Endring på pasient" Returns a list with one task for each patient having changes in medication in Kjernejournal since the _lastUpdated time.

General TASK operations

Create operation on Task is not available

Delete operation on Task is not available

Search operation directly on Task without given code will not trigger a lookup in national systems

Search operations on Task other than described here have an unpredictable result

Format of returned info

The most relevant action for sfm-Task is the search operations defined. The format of the return is a search bundle containing tasks. Each task will have a "Patient" referred from for field. This reference is to a contained sfm-Patient within the Task.

Profile

sfm-Task

Task

Task.instantiatesCanonical

Task.instantiatesUri

Task.basedOn

Task.groupIdentifier

Task.partOf

Task.status

Task.statusReason

Task.businessStatus

Task.intent

Task.code

Task.code.coding.system

http://ehelse.no/fhir/CodeSystem/sfm-task-types

Task.code.coding.code

Task.code.coding.display

Task.description

Task.focus

Task.for

Task.encounter

Task.executionPeriod

Task.authoredOn

Task.lastModified

Task.requester

Task.performerType

Task.owner

Task.location

Task.reasonCode

Task.reasonReference

Task.insurance

Task.note

Task.relevantHistory

Task.restriction

Task.input

Task.output