This data model allows you to locate a patient record based on incomplete identifying information. You can search for a patient by:
- Identifier: Search with an identifier like the patient's MRN. Review tips for searching with a patient identifier.
- Demographics: Search with a patient's name, birthdate, gender, or Social Security number (SSN). Review tips for searching with demographics.
You can only search for a patient at one organization at a time. If you want to search for a patient at multiple organizations, you can use this data model in conjunction with Network Onramps to search a clinical network. Learn about options for patient searches.
This data model has event types that allow you to:
- query for or receive patient records; or
- query for and receive a location's information about a patient.
Query with a known patient identifier to find locations that may have a patient's clinical information.
You can use this event type with Network Onramps to query with a network patient ID to a record locator destination. Learn more about searching for patient records within a clinical network.
Request Body Schema
- Metarequired, object
- DataModelrequired, stringReliable
PatientSearch
- EventTyperequired, stringReliable
LocationQuery
- EventDateTimestring, nullReliable
Displays the UTC date and time that an outgoing request is delivered or an incoming request is received.
ISO 8601 Format - Testboolean, nullReliable
Indicates whether the request is a test or not.
- Sourceobject
Contains the information for the system initiating the message, including the source ID and name.
Included in messages from Redox- IDstring, nullReliable
Identifies the system initiating the message. If you have multiple OAuth API keys per environment type, this value is required. If you have only one OAuth API key per environment type, or you're using legacy API keys, this value is optional.
UUID - Namestring, nullReliable
Displays the name of the system initiating the message.
- DestinationsArray of object
Contains the information for the endpoint(s) receiving the request. A request must contain at least one destination, but asynchronous requests can have more than one destination. Synchronous requests like queries can only support one destination.
Required when sending data to Redox.- IDstring, nullReliable
Identifies the endpoint that the request is directed to.
UUID - Namestring, nullReliable
Displays the name of the endpoint that the request is directed to.
- LogsArray of object
Contains the log identifier(s) for the request.
- IDstring, nullReliable
Identifies the request log(s) that correspond to this request. You can use this value to locate the relevant log in the Redox dashboard for support and reference.
UUID - AttemptIDstring, nullReliable
Identifies the request log attempt value, which is useful when retries are possible.
UUID
- FacilityCodestring, nullPossible
Code for the facility related to the message.
Only use this field if a health system indicates you should. The code is specific to the health system's EHR and might not be unique across health systems. In general, the facility fields within the data models (e.g. OrderingFacility) are more reliable and informative.
- Patientrequired, object
- Identifiersrequired, Array of object
List of IDs and ID types that identify the patient
- IDrequired, stringReliable
ID for the patient
- IDTyperequired, stringReliable
Type of ID.
E.g. MRN, EPI