This data model communicates discrete clinical data to or from an EHR system. Flowsheet data includes both inpatient and outpatient data, including assessment information, vitals, patient-reported outcomes or questionnaires, and any other discrete clinical documentation.
This data model has event types that allow you to:
- provide continuous vitals or assessments to a patient's chart.
Add new observations to the flowsheet. Multiple observations may be included in one message.
Request Body Schema
- Metarequired, object
- DataModelrequired, stringReliable
Flowsheet
- EventTyperequired, stringReliable
New
- 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
- Demographicsobject
- FirstNamestring, nullReliable
Patient's first name
- MiddleNamestring, nullPossible
Patient's middle name or middle initial. For patients with multiple middle names, all their middle names are included in this field.
- LastNamestring, nullReliable
Patient's last name
- DOBstring, nullReliable
Patient's date of birth.
In ISO 8601 format - SSNstring, nullProbable
Patient's social security number
- Sexstring, nullReliableValue Set
Patient's sex
- Racestring, nullPossibleValue Set
Patient's race
- IsHispanicboolean, nullPossibleValue Set
Indicates if the patient is of hispanic origin.
- Religionstring, nullPossibleValue Set
Patient's religious affiliation
- MaritalStatusstring, nullPossibleValue Set
Patient's marital status
- IsDeceasedboolean, nullPossible
Indicates if the patient is deceased
- DeathDateTimestring, nullPossible
Date and Time the patient was proclaimed deceased.
ISO 8601 Format - PhoneNumberobject
- Homestring, nullProbable
Patient's home phone number.
In E. 164 Format. (e.g. +16085551234) - Officestring, nullProbable
Patient's office phone number.
In E. 164 Format. (e.g. +16085551234) - Mobilestring, nullProbable
Patient's mobile phone number.
In E. 164 Format. (e.g. +16085551234)
- EmailAddressesArray of string
Patient's email address(es)
- Languagestring, nullPossibleValue Set
Patient's primary spoken language.
In ISO 639-1 alpha values (e.g. 'en'). Supported Values - CitizenshipArray of string
Patient's nation(s) of citizenship.
In ISO 3166 alpha 2 format (e.g. 'US'). - Addressobject
Patient's home address
- StreetAddressstring, nullProbable
Street address
- Citystring, nullProbable
City
- Statestring, nullProbable
State
- ZIPstring, nullProbable
ZIP
- Countystring, nullPossible
County
- Countrystring, nullPossibleValue Set
Country
- NotesArray of string
Patient-level notes
- ContactsArray of object
- FirstNamestring, nullPossible
First name of the contact
- MiddleNamestring, nullPossible
Middle name of the contact
- LastNamestring, nullPossible
Last name of the contact
- Addressobject
Address of the contact
- StreetAddressstring, nullPossible
Street address
- Citystring, nullPossible
City
- Statestring, nullPossible
State
- ZIPstring, nullPossible
ZIP
- Countystring, nullPossible
County
- Countrystring, nullPossibleValue Set
Country
- PhoneNumberobject
- Homestring, nullPossible
Home phone number.
In E. 164 Format. (e.g. +16085551234) - Officestring, nullPossible
Office phone number.
In E. 164 Format. (e.g. +16085551234) - Mobilestring, nullProbable
Mobile phone number.
In E. 164 Format. (e.g. +16085551234)
- RelationToPatientstring, nullPossibleValue Set
Personal relationship to the patient.
e.x. Father, Spouse - EmailAddressesArray of string
Email address(es) of the contact person
- RolesArray of string
Role of this contact for the patient.
e.x. Employer, Emergency Contact
- Observationsrequired, Array of object
List of values to be added to the flowsheet
- DateTimerequired, stringReliable
DateTime the value was recorded.
ISO 8601 Format - Valuerequired, stringReliable
Value to be recorded.
For example, if the value is a heart rate, this will be 65 - ValueTyperequired, stringReliableValue Set
Data type of the value
- Coderequired, stringReliable
Code for the flowsheet row that the value should file to.
This is usually provided by the EMR or you will asked to provide a list of codes you can send. For example, this is where you would specify "Heart Rate" for heart rate values. - Unitsstring, nullProbable
Units of the value.
If the Code is "Heart Rate", this may be "BPM" - Codesetstring, nullProbable
Codeset used to identify the code
- Descriptionstring, nullProbable
Description of the flowsheet row
- Statusstring, nullPossibleValue Set
Status of the observation
- NotesArray of string
Notes about the observation
- Observerobject
- IDstring, nullPossible
Optional code indicating who made the observation.
Typically represents an actual person, but may also be linked to device in some EHRs - IDTypestring, nullPossible
ID type of the ID for the Observer
- FirstNamestring, nullPossible
Optional code indicating who made the observation
- LastNamestring, nullPossible
Optional code indicating who made the observation
- ReferenceRangeobject
Reference range for the observation.
Numeric observation values will use the low and high properties. Non-numeric observation values will put the normal value in the text property.- Lownumber, nullPossible
Lower bound for a normal observation
- Highnumber, nullPossible
Upper bound for a normal observation
- Textstring, nullPossible
The normal value for non-numeric observations
- AbnormalFlagstring, nullPossibleValue Set
Indication of whether the observation was abnormal.
One of the following: "Normal", "Low", "Very Low", "High", "Very High", "Abnormal", "Very Abnormal". Abnormal flags starting with "Very" indicate a panic level. The "High" and "Low" flags should be used with Numeric result values while "Abnormal" should be used with non-numeric values.
- Visitobject
- VisitNumberstring, nullReliable
Number for the visit that contains the flowsheet.
VisitNumber is highly recommended so that the document can be associated with a specific visit - AccountNumberstring, nullPossible
Account Number.
An ID that can span several visits often related to the same issue - pregnancy, surgeries, research study, etc. - VisitDateTimestring, nullPossible
DateTime of visit or appointment.
ISO 8601 Format - Locationobject
Location of the patient. This may be used for validation or to identify your application/device.
- Typestring, nullProbable
Type of location.
Examples: Clinic, Department, Home, Nursing Unit, Provider's Office, Phone - Facilitystring, nullProbable
Facility.
Example: Community Hospital - FacilityIdentifiersArray of object
List of IDs specific to this facility
- IDstring, nullProbable
An ID specific to this facility
- IDTypestring, nullProbable
The source or system to which this ID pertains.
Could be an OID or a human-readable name
- Departmentstring, nullProbable
Department
- DepartmentIdentifiersArray of object
List of IDs specific to this department
- IDstring, nullProbable
An ID specific to this department
- IDTypestring, nullProbable
The source or system to which this ID pertains.
Could be an OID or a human-readable name
- Roomstring, nullProbable
Room.
Example: 136 - Bedstring, nullProbable
Bed.
Example: B