# Receive a request for patient monitoring

You can use this API action if your organization provides some type of patient monitoring, whether via a device, app, or both. 

## Use cases

This API action may be a good fit for your organization if you perform any of these use cases:

- Receive orders from a provider for a device to monitor a patient.
- Receive orders from a provider for nursing or app monitoring.

## Supported systems

You can receive messages like this with the Redox FHIR API.

> **Talk to a Redoxer**
>
> It’s also possible to use the Redox Data Model API for this API action. [Talk to a Redoxer](https://redoxengine.com/forms/contact-us/) to learn about your options.

Your connection's system can send messages with their own FHIR or proprietary API or an HL7v2 feed.

> **Lightweight or detailed notification**
>
> Depending on your connection’s capabilities, you can opt in for lightweight or detailed notifications.
>
> A <u>lightweight</u> notification is typically a bare bones message with the relevant identifier (e.g., patient, visit #) and an indication of “something's new” or “something has changed.” Lightweight notifications generally trigger you to do something within your own workflow or to query for more information.
>
> On the other hand, a <u>detailed</u> notification means that you receive all the data about what’s new or what's changed. This might be useful if you need to persist all that data in your system to complete your own unique workflow.

## Things you need to know

<details>
<summary>New EHR order for patient monitoring</summary>

Given all the possible variety, a patient monitoring order isn’t standardized. This means that the EHR system _must_ create an order within their catalog to send this kind of message to you. 

During implementation, most EHR systems allow you to design the order details so that you get the information you need and the clinician knows what to enter for this type of order. We recommend keeping your requirements to a minimum so that the EHR system can best support it.  

For remote patient monitoring, the order details typically include questions about the monitoring schedule or clinical diagnosis. 

</details>

<details>
<summary>Follow-up actions for monitoring</summary>

Since you’re doing some kind of monitoring for the patient, you'll likely have to send vitals or report the data to the healthcare organization that requested monitoring. Work with your connection to find out what data they want and how to provide it back to them. We recommend this so you can support any other relevant API actions to complete your workflow from start to finish.

</details>

> **What's next? **
>
> Does this API action seem like a good fit for your unique workflow? Let your Technical Account Manager know! To start development, download the resource schema noted in the related action step. Then decide which data elements you need.
>
> If you’re new to Redox, [use the Quickstart guide](/quickstart-for-redox) to dive in. If you’re not engaged with our sales team yet, [talk to a Redoxer](https://redoxengine.com/forms/contact-us/) to get started.