Understanding the Redox Results Data Model

When do I need to use the Results Data Model?

The Redox Results Data Model is used to transmit discrete clinical data to or from an EHR. Typically this model is applicable in situations where an application is sending a one-off value, many times the result of some kind of physician-entered order, to the patient’s chart. This data will show up wherever results are in the EHR.  Some examples that commonly involve the Results Data Model:

  • Labs
    • General lab (discrete lab values)
    • Microbiology (discrete, structured lab data pertaining to antibiotic sensitivities)
    • Pathology (result reports after reviewing pathologic images)
  • Diagnostic imaging/image-like areas
    • Radiology (result reports after reviewing radiologic images)
    • Cardiology (result reports and/or discrete data after reviewing cardiology images)
    • Urology (urination tests)
    • Pulmonology (lung function test)
    • Neurology (EEGs and result reports)
    • Obstetrics (fetal echos and result reports)

What form of data do applications send or receive using the Results Data Model?

Results data can be filed back in various formats depending on EHR capability:

  • Discrete information, such as specific lab and cardiology values
  • Textual information, such as a pathology report
  • A PDF or other complex data formats (JPEG, Word, etc) for the test (such as a document that shows a graph of lung function)
    • Applications can embed the document in the message using an encoding scheme called base64. The EHR can then pull this embedded document out of the message and store it in their database. For more information on that check out our Sending Files through Redox post.
    • Applications may store the PDF or file on their own server and send a reference pointer (a URL or file destination). The EHR then would render the link to view the document.

How is the Results data model different from the Flowsheets Data Model?

The main difference between these models is where the data will end up within an EHR destination. The Flowsheet Data Model is more appropriate for workflows where the same type of discrete data is being measured and reported regularly. A number of EHRs support some kind of flowsheet activity where this data will show up and viewed together, which makes identifying trends easier. The Results model is usually better suited to situations where a one-off value, many times the result of some kind of diagnostic test order that was placed for a patient, is being sent to the patient’s chart. This data will show up wherever results are in the EHR.