Managing tasks
Introduction
When a user opens EPJ, or functions that show tasks to the user, the sfm-Task resource should be used.
The resource is avaialble to make it possible for EPJ systems to present an updated tasks list to the user. Initially, SFM indicated support for "machine token" (without user identity). This is still not implemented, and a normal tolken with user identity must be used.
Only the command GET is made available for epj-systems.
Read task list
- User opens EPJ
- EPJ request SFM for open tasks that needs to be solved by the user.
- SFM returns tasks dedicated to the user and tasks that can be solved by any user.
- EPJ presents the tasks to the user.
Input parameters
- Type
- code:not
- PatientTicket
Task searching by Type
The following combinations are accepted for Type:
| Type | Description |
|---|---|
| None | Returns all tasks for whole installation without MD (multidose) - to be used within other installations than GP (general practitioner = fastlege) and PLO (pleie og omsorg = nursing and care). |
| MD | Returns all tasks for whole installation with multidose (MD) lookup on each multidose patient - to be used within GP installations |
| NonePatient | Returns all none patient related tasks |
Example on how to use Type:
/Task?type=MD
/Task?type=None
/Task?type=NonePatient
Task exclusion
In some settings the user must be able to exclude selected types of tasks. For example, when drafts are not relevant and should not be loaded the code:not parameter can be used. The code can be found in Task types .
Drafts are not returned in following example
/Task?codeNot=3
Excluding more than one task type can be done as follows
/Task?codeNot=3,5,6
Calling a type and excluding a task is done like this
/Task?type=MD&codeNot=3
Tasks search by individual patient
Task can now be searched based on an individual patient. Note that now you will need to request:
/Task?PatientTicket=[actual ticket]
Return from SFM will include the following attributes:
- identifier
- status
- intent
- code (See Types of tasks below)
- description
- for (if there is identifed a patient that is benefisary of the task is performed).
- owner (Practitioner identified with HPR AND DNR/FNR, or Organization) (valid from SFM version 4.0). HPR should be the preferred identifier for Practitioner, as FNR/DNR may be removed in the future.
Tasks for each patient that are the same type are aggretated into a single task.
Description includes details about the task. For aggregated tasks, the description includes aggregated information. eg. "4 resepter og 2 tilbakekallinger klar for sending".