Questions and Answers > Understanding the Redox Media Data Model
Questions and Answers

Understanding the Redox Media Data Model

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 a file (JPEG, PDF, WAV, etc), they should be using the Media Data Model.

Media is a good choice for applications that want to write information back to EHRs, as it offers a lot of flexibility about what content can be stored (almost any content can be put into a PDF), control over how it’s shown, and support across EHRs.

How is the Media Data Model different from the Note Data Model?

Media Data Model is similar to the Note Data Model, in that both are often used for sending a summary back to an EHR. They differ in that:

  • Layout:
    • Media, when sent as a PDF, has a guaranteed layout that is consistent across EHRs.
    • Notes sent as plain text or rich text are subject to the rendering capabilities of the EHR.
  • Direct Display:
    • Media is generally represented as a link (a user clicks a link to launch a separate program to show the PDF, play the WAV, display the JPEG, etc).
    • Notes are shown within the EHR context.
  • Searchability and Analytics:
    • Notes may offer superior searchability (if the EHR has that capability) and usability for things like Natural Language Processing (where software analyzes the note content for things like diagnoses, problems, and medications and offers them to the user to be added discretely)

What file types can be transmitted through the Media model?

Ultimately this is dependent on the file types that are supported by the connecting health system. In addition to PDF documents we’ve seen health systems support transmission of image files such as PNG, TIF and JPEG files as well as WAV audio files.

What data is required in order to file Media documents to the patient’s chart?

This will depend on how the users want to access the information within their EHR and the information needed by the EHR to file it as expected.  To file a document to the patient’s chart for general information purposes, most EHRs will require the patient identifier in addition to other basic patient demographics such as name and DOB. Additional required items include relevant provider information (i.e. who generated the document), the file type, the file name, a unique document ID, and whether or not the document has been authenticated and is authorized to be shared in the patient’s chart.  To file a document to a specific visit or to show up associated with specific areas or actions in the EHR, a visit number is often required to provide more specificity.

How do I send the files over the Redox Media data model?

Media files under 200KB can be sent directly to the API as base64 encoded strings over the Redox Media Data Model. Files over 200kb will first need to be uploaded to the Redox blob endpoint, which will synchronously return the file URI that can then be specified in a Media message. You can read more about that here.

Can I send embedded documents over other Data Models?

Redox has support for embedded documents across other data models such as Results and Notes, limited only by corresponding support from EHRs. If interested, please reach out to your Redox representative.

What about DICOM? Isn’t that a sort of file?

Most EHRs don’t use the Media Data Model to receive diagnostic quality images, which typically are stored in a Picture Archive System. Generally, if an EHR does store some images, these will be reference images such as JPEG, PNG, or GIF that can be stored via Media. Additionally, sending DICOM, which can be very large files, is likely above EHR file size limits for Media.