Questions and answers for different Redox Data Models
When do I need to use the Media Data Model? The Media Data Model is used to exchange photos, videos, and audio recordings, as well as images/documents to and from a patient’s chart. Essentially, if an app wants to pass or receive…
When do I need to use the SurgicalScheduling Data /model? The SurgicalScheduling Data Model is used to receive surgical case information, such as staff assigned to the surgery, case and procedure details, location, etc. This may come from an OR specific system or…
When do I need to use the Scheduling Data Model? Applications use the Scheduling Data Model to communicate information surrounding a patient’s appointments. At certain events in the normal scheduling process (scheduling, rescheduling, arrival/check-in, check-out), EHRs will send scheduling messages to keep…
When do I need to use the PatientAdmin Data Model? The PatientAdmin Data Model is the most common feed used across Redox customers and is something we would recommend you require if you persist patient data in your application. Over 90% of our…
The Redox Single Sign-on data model abstracts away various vendor authentication strategies, such as the SAML Web Browser Profile, SMART on FHIR, or url-based SSO strategies. How Redox Sits in between you and SSO All single sign-on schemes hinge on validating that a user is who…
When do I need to use the ClinicalSummary data model? If your application is looking to receive a patient’s clinical information, either historical or in real time, then our ClinicalSummary data model is for you. This model is based on documents that…
The healthcare industry is infamous for its aggressive use of acronyms that often confuse people more than they help. Chief among these is the term CCD… and CDA, C-CDA. Though similar in both name and function, these terms don’t always mean the…
Contact Redox if you need help deleting a user from your organization. To chat with us directly, you can click the button in the bottom right-hand corner of your screen!
Short answer – nope! Long answer – still nope! You will have 4 records – 2 in Staging (1 Source record, 1 Destination record) and 2 in Production (1 Source record, 1 Destination record). Each of these 4 records has its own respective ID.…
No! We intentionally don’t place limits or structure pricing around a specific number of API calls because we want our pricing to be transparent and predictable for our partners. This way, they will know exactly how much integration costs, whether it is…