MedicationRequest _search

post/MedicationRequest/_search

Page View

This resource contains a list of a patient’s current prescribed medications, as documented by one organization. What this doesn’t contain: any details about how much a patient has taken of what they were prescribed.

You can review, retrieve, or create a list of current medications for a patient.

Supported fields and schema examples

We support any valid FHIR® field. However, we only display fields we’ve defined in our schema, which are usually based on what’s included in the U.S. Core profile. We recommend relying on U.S. Core requirements.

Our schema examples show the shape and possibility of each FHIR® resource; they aren’t code for real-time API calls. We don’t currently recommend copying and pasting these schema examples for your API calls. Consider reviewing FHIR® API actions for realistic examples for particular use cases.

_search

Query for a list of current medications for a patient. Review tips for medication searches.

Flexible FHIR queries, different query parameters

FHIR® queries are a flexible option with parameters to refine your search. The response returns a bundle of resources, known as a searchset bundle type. Learn about bundles and bundle types in our FHIR® glossary.

We only note which query parameters are required if you're querying a FHIR® server directly. Remember that Redox (i.e., data on demand) isn't a FHIR® server, and your connection may not be either.

Query parameters will vary between sites. Work with your connection to find out which query parameters they require for a successful search.

Data on demand requirements

For data on demand searches, you must include this query parameter:

FHIR® resource ID for Patient resource (learn about FHIR® references or review HL7's docs on references)

Request parameters and payload

cURL request example

bash

1
curl 'https://api.redoxengine.com/fhir/R4/{destinationSlug}/{environmentFlag}/MedicationRequest/_search' \
2
--request POST \
3
--header 'Authorization: Bearer $API_TOKEN' \
4
--header 'Content-Type: application/x-www-form-urlencoded' \
5
--data-urlencode 'patient=string' \
6
--data-urlencode 'patient.identifier=string' \
7
--data-urlencode 'intent=string' \
8
--data-urlencode 'status=string' \
9
--data-urlencode 'recorder=string' \
10
--data-urlencode 'authoredon=string' \
11
--data-urlencode 'requester=string' \
12
--data-urlencode 'encounter=string' \
13
--data-urlencode 'encounter.identifier=string'

Request Body Schema

patient
Array of string
Returns prescriptions for a specific patient
patient.identifier
Array of string
One or more external identifiers for the patient
intent
Array of string
Returns prescriptions with different intents
status
Array of string
Status of the prescription
recorder
Array of string
Person who entered the request
authoredon
Array of string
When request was initially authored
requester
Array of string
Person who prescribed this medication
encounter
Array of string
Encounter during which the medication was prescribed
encounter.identifier
Array of string
Identifier(s) by which this encounter is known

Response fields and example

Example payload generated from schema

1
{
2
  "resourceType": "Bundle",
3
  "type": "searchset",
4
  "total": 1,
5
  "entry": [
6
    {
7
      "resource": {
8
        "resourceType": "MedicationRequest",
9
        "id": "RedoxClinicalSummaryMedicationRequestCodeExample",
10
        "identifier": [
11
          {
12
            "system": "urn:oid:1.2.840.114350.1.13.12345.1.7.2.798268",
13
            "value": "865492246"
14
          }
15
        ],
16
        "subject": {
17
          "reference": "Patient/RedoxPatientExampleTimothy"
18
        },
19
        "intent": "order",
20
        "encounter": {
21
          "reference": "Encounter/RedoxEncompassingEncounterExample"
22
        },
23
        "medicationCodeableConcept": {
24
          "coding": [
25
            {
26
              "code": "104894",
27
              "system": "http://www.nlm.nih.gov/research/umls/rxnorm",
28
              "display": "Ondansetron 4 Mg Po Tbdp"
29
            }
30
          ],
31
          "text": "Ondansetron 4 Mg Po Tbdp"
32
        },
33
        "dispenseRequest": {
34
          "quantity": {
35
            "value": 30,
36
            "unit": "tablet"
37
          },
38
          "numberOfRepeatsAllowed": 0,
39
          "validityPeriod": {
40
            "start": "2019-04-01T00:00:00.000Z",
41
            "end": "2019-05-31T00:00:00.000Z"
42
          },
43
          "performer": {
44
            "reference": "Organization/RedoxOrganizationPharmacyExample"
45
          }
46
        },
47
        "status": "active",
48
        "priority": "routine",
49
        "reasonCode": [
50
          {
51
            "coding": [
52
              {
53
                "code": "422587007",
54
                "system": "http://snomed.info/sct"
55
              }
56
            ],
57
            "text": "Nausea"
58
          }
59
        ],
60
        "authoredOn": "2019-04-01T17:04:16.605Z",
61
        "requester": {
62
          "reference": "Practitioner/RedoxPractitionerExampleMedicationRequest"
63
        },
64
        "recorder": {
65
          "reference": "Practitioner/RedoxPractitionerExampleMedicationRequest"
66
        },
67
        "dosageInstruction": [
68
          {
69
            "text": "one tablet every morning",
70
            "asNeededBoolean": false,
71
            "route": {
72
              "coding": [
73
                {
74
                  "code": "C38288",
75
                  "system": "urn:oid:2.16.840.1.113883.3.26.1.1",
76
                  "display": "Oral"
77
                }
78
              ]
79
            },
80
            "doseAndRate": [
81
              {
82
                "doseQuantity": {
83
                  "value": 4,
84
                  "unit": "mg"
85
                }
86
              }
87
            ],
88
            "timing": {
89
              "repeat": {
90
                "when": [
91
                  "MORN"
92
                ],
93
                "boundsPeriod": {
94
                  "start": "2013-11-11T05:00:00.000Z"
95
                }
96
              }
97
            }
98
          }
99
        ]
100
      },
101
      "search": {
102
        "mode": "match"
103
      }
104
    }
105
  ]
106
}

Response to a MedicationRequest search operation

resourceType
required, string
Identifies the type of the resource
Value: Bundle
type
required, string
Identifies this bundle as a response to a search
Value: searchset
total
required, number
The total number of matches
entry
Array of MedicationRequest or Other
A resource matching the search criteria or related to a matching resource

FHIR® is a registered trademark of Health Level Seven International (HL7) and is used with the permission of HL7. Use of this trademark does not constitute an endorsement of products/services by HL7®.