Redox data models contain the most common, industry-standard data fields, but they don’t cover every possible use case. When your workflow requires specific data that isn’t in the standard—for example, an appointment’s confirmation status—we offer extensions to add those fields.
When supported, a data model might have multiple extensions. Also, an extension container can have one or more extensions within it.
We review whether the data is critical and can be supported before adding an extension. Not all connections may support extensions.
Most healthcare standards don’t account for representations of gender identity, sexual orientation, ethnicity, or disability.
At Redox, we value belonging. It’s important to us to support this diversity data when it’s available from your connection. We offer extensions on every data model to support diversity-related information. If your connection can send or receive diversity data, you can do so with Redox without needing to upgrade to a higher platform tier.
An extension applies to a specified data model, event type, and field. The Extensions container holds extension objects. The key of the object (e.g., additional-phones) identifies the extension, and the value contains the extension’s data. An optional url field can also be included for reference.
We offer an Additional Phone Numbers extension for these data models.
Data model | Event types | Available fields for extension |
|---|---|---|
PatientAdmin | All | Patient.Demographics.PhoneNumber Patient.Guarantor.PhoneNumber Patient.Contacts[].PhoneNumber |
Scheduling | All | Patient.Demographics.PhoneNumber Visit.Location |
When used for any available fields, the Additional Phone Numbers extension contains values for extra home, office, or mobile phone numbers for the patient or location.
The top-level key has the name of the extension. The value for that top-level key can include the extension URL.