Data Model (Parsed Data)

A Data Model defines layout and structure of how all data is represented and perceived.  Our Data Model, known as the “Parsed Data Block” is a well-defined XML based structure, that allows us to map any known data point for a given patient message (i.e. CCD/CDA, HL7, FHIR, CSV) to a specific spot in the Canonical Model. 

For instance, when looking at a message with our Parsed Data Block, the name of a patient will always be found at the XML Path: /Document/Patient/Name and having possible attributes like @first,@last, @full and so on, regardless of what type of message was given.  Paths like this exist for each and every possible piece of patient data.

After years of working with the various healthcare standards, we have mapped most every data source type into and back out of our Canonical Model. We have packaged these libraries and several tools into our Alchemy system, “turning your healthcare data into gold.”

This allows us to immediately convert ANY source data from its original state INTO our model, perform any work we want on it, and send it back out either as the original format, or even as a different one. 

The beauty of this design is that once it is in the Canonical Model, any developer that understands basic XML can then work with the data, and either build triggers, modifiers, or analysis tools. 

PhysBee

Our take on a Universal Health Record (UHR), or more popularly as a Patient Health Record (PHR).

Based on 20 year fortified CDR-Web base data model

Facebook like user-interface for ease-of-access and entry

PhysBee is an all-encompassing patient managed medical record. While Physbee can be tied to Populous and other EHRs, it also accepts patient input of their clinical record, regardless of location.

With Physbee a part of your suite of clinical applications, you enable your patients and give them command of their clinical data. Physbee is useful for many reasons, but most needed in emergency situations.

Let’s see how PhysBee helped Mary Smith. (Mary Smith is not her real name)

Mary lives in Michigan and has managed her Physbee patient record for three years. Her patient record has her providers’ details and contact information, discharge summaries, the 5 medications she takes, lab and radiology results and more. Mary’s A1C was being monitored. However, she has seen her physician less frequently lately. She is unaware that she has developed diabetes. Mary travels to Florida. There, she faints and falls. At Urgent Care, Mary confidentially shares her Physbee patient record, saving providers valuable time in their diagnosis. Mary is well taken care of and her case is quickly resolved.

ADT Notification System

The ADT Notification module of PhysBeeMD (PAN) application supports the State-wide ADT Notification Service, as well as any entity which has access to one or more hospital ADT feeds. The PAN converts ADT events and data into useful, readable clinical information so health care professionals can make decisions with a more complete view of their patients.

Lab Reporting System

The Lab Reporting module of PhysBeeMD (LRS) application supports the State-wide Lab Reporting Service, as well as any entity which has access to one or more Lab feeds. The LRS converts HL7 Lab events and data into useful, readable clinical information so health care professionals can make decisions with a more complete view of their patients.