In this article, we share best practices and tips if you're a health tech vendor that needs to send the Order.New event type to your connection via the Redox Data Model API.
In our experience, healthcare organizations that process new orders commonly ask for the data listed in the table below. These aren't the full requirements, only high-level suggestions when you're getting started. Refer to the Order schema for full technical details and requirements.
Data | Notes |
|---|---|
Patient name | Who the order is for. |
Patient identifier in your connection's EHR system | This means you must be able to support a patient search or read to first find the patient identifier in your connection's system. |
Provider name | Who should fulfill the order for the patient. |
National Provider Identifier (NPI) | This is the provider's unique national identifier. |
Procedure code | This code should match the procedure code in the EHR system. For example, if you’re sending an order for an abdomen CT, you must include the procedure code that the EHR system specifically uses for abdomen CTs. For this to work, you must have already set up procedure mapping between connections during your implementation. That's an essential step to match your list of procedures to the related procedure codes in the EHR system. |