Page Status: updated 2022-11-03
Create NLLDataLock (Basic)
Page index
Introduction
sv. Skapa spärr.
This page describes how to create secrecy locka and privacy locks (data locks) for a patient by a few examples.
Before a DataLock is created, the user needs access to other information in the National Medication List. For more information on different scenarios and what information is required for each scenario, see Handbok för vård- och apotekstjänster: Verksamhetsområden.
Request
Creating a data lock is done by the following operation.
POST [base]/Basic
Request Headers
A set of HTTP headers must be provided in order to create a data lock and the data lock itself is provided as a Basic of type DataLock in the HTTP body.
The authorization token is translated to an authority role. The authority role together with the purpose and type of access is used by the National Medication List to determine what actions a user may perform and what information the user may access.
| Header | Comment |
|---|---|
| authorization | The users's security token |
| prefer | Type of returned content |
| x-access | The cause for the call |
| x-context-id | An ID to group a sequence of requests |
| x-org-info | Information about the users's organisation |
| x-patientref | The logical ID of the patient |
| x-provenance | A provenance resource with information about the user interacting with NLL |
| x-purpose | The purpose of the call |
| x-request-id | A random and unique ID |
| x-user-agent | Information about the calling system |
Request Body
See NLLDataLock for more information about the DataLock resource.
Examples
Example 1 - Create an privacy data lock
This example shows how an privacy data lock is created. The privacy lock is created by the prescriber on behalf of the patient.
Request Headers
| Header | Value | Comment |
|---|---|---|
| authorization | {...,"FORSKRIVARKOD":"9000027","VARDGIVARE":"0123456789","YRKESKOD":["LK"],"loa":3} |
Selected information from the OAuth2-ticket in decoded form |
| x-org-info | {"orgenhetsOrt":"Sala"} |
Decoded value |
| x-provenance | Provenance for a patient | Decoded value |
| x-request-id | 83cf13d5-18f2-4548-bae0-219ed3de9e7e |
|
| x-user-agent | {"name":"Test application","version":"0.01010101010.1 beta"} |
Decoded value |
Request Body
See Create DataLock - privacy lock of a prescription chain.
Example 2 - Create a secrecy data lock
This example shows how a healthcare professional creates a secrecy data lock so the patient can't see the cause of treatment of a prescription chain.
Request Headers
| Header | Value | Comment |
|---|---|---|
| authorization | {...,"FORSKRIVARKOD":"9000027","VARDGIVARE":"0123456789","YRKESKOD":["LK"],"loa":3} |
Selected information from the OAuth2-ticket in decoded form |
| x-org-info | {"orgenhetsOrt":"Orgsala"} |
Decoded value |
| x-provenance | Provenance for a healthcare user | Decoded value |
| x-request-id | a449f092-b16b-4e41-aca5-883952a9a794 |
|
| x-user-agent | {"name":"Test application","version":"0.01010101010.1 beta"} |
Decoded value |