Page Status: updated 2022-11-03

Medication List Info (Basic) - Fetch

Page index

Introduction

Sv. Hämta information om patients läkemedelslista.

This page describes how to fetch the resource Basic of type MedicationListInfo for a patient by an example.

A MedicationListInfo can be fetched in different ways. See MedicationListInfo query operations for information about all options.

In short, a query request is either a read, that is, a retrieval via the resource ID, or a search via a search condition. The result differs between a read and a search. A search results in a Bundle being returned containing all matching resources. If there are no hits, an empty Bundle is returned. A read results in the requested resource being returned or an error if no resource with the requested ID exists. If a system error occurs both searches and reads result in an error (i.e. an OperationOutcome).

Fetching a Basic of type MedicationListInfo is done by one of the following operations.

GET [base]/Basic/[id]
GET [base]/Basic?code=medlistinfo&[search parameters]

A set of HTTP headers must be provided in order to fetch a MedicationListInfo. See HTTP Header and Authorization for more information about the various headers used by the National Medication List.

See NLLMedicationListInfo for more information about the MedicationListInfo resource.

Before a MedicationListInfo can be retrieved and presented to the user other information is needed from 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.

Examples

HTTP Headers

See HTTP Header and Authorization for generic information about all HTTP headers used by the National Medication List including information about authorization, purpose and access type. 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

Example 1 - Fetch a patient's Medication List Info

This example shows a summary of a patient's medication list based on the content of the National Medication List.

The request is made as a search by the logical id of the patient, GET [base]/Basic?code=medlistinfo&patient._id=b00a0407-b781-43e8-983b-74fdfb8eb97d.

HTTP headers

Header Value Comment
authorization {...,"FORSKRIVARKOD":"9000027","VARDGIVARE":"0123456789","YRKESKOD":["LK"],"loa":3} Selected information from the OAuth2-ticket in decoded form
prefer
x-access TILLFALLIGT_SAMTYCKE
x-org-info {"orgenhetsOrt":"Sala"} Decoded value
x-patientref b00a0407-b781-43e8-983b-74fdfb8eb97d
x-provenance
x-purpose VARD
x-request-id 86a799bb-b14e-4da4-8daf-3d9c1fcea25b
x-user-agent {"name":"Test system testaren","version":"0.01010101010.1 beta"} Decoded value

HTTP body: Fetch MedicationListInfo