The Redox Engine platform allows you to access and interact with a wide variety of healthcare-related data via a consistent, normalized, REST-inspired API. Our platform is based on a truly standardized data model and format and uses HTTPS communication with JSON to allow you to securely and conveniently build the next generation of innovative healthcare applications.
Our Data Models are divided into categories based on subject. Some categories are event based: Scheduling and PatientAdmin are examples of this, where messages are triggered based on some user action in the EHR (a new appointment is scheduled, or a new patient is registered, etc). Other Data Models are request based. ClinicalSummary – Query is an example of this, where we grab the Clinical Summary and pass it back to you on demand, rather than based on some real-time event in the EHR.
Each Data Model can have multiple events underneath it, based on the types of events or queries that generate the message. PatientAdmin, for example, has many, many event types, of which we support quite a few. For each Event, the Data Model may look a little different, as different information is passed from the EHR depending on the event that took place.
Fields / Data Consistency / Required Fields
Each Data Model is made up of key/value pairs in a JSON structure. For each Data Model, we specify which fields are present in which Data Models. Pay particular attention to the Consistency and Required badges. We can only pass on the data that we have access to, and from health system to health system and vendor to vendor, some fields may or may not be available to us. We do our best to work with each health system to get as much data as possible, but there will always be some differences. Part of the testing process will be to identify which fields we can rely on for a given health system. For messages sent to us from your application, we require some fields to ensure we can pass enough information to the health system for the message succeed.