A Canonical Data Model defines “What is Canon”, and lays out a structure of how all data is represented and perceived.  Our Canonical 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. 

The SQL Data Model is a third-normal-form based model, with nearly all tables using large integer Identity based keys, providing performance and referential integrity.  The Data Model began with our Clinical Data Repository (CDR-Web), focusing on the primary portions of a patient record: Demographics, Procedures, Diagnoses, Lab Results and so on.  In CDR-Web’s product evolution, this expanded to include Order Entry, Medications, Pharmacy Order Entry, and Scanned Documents. 

During our partnership with HFHS for EXR/CPNG, our data model was chosen for the basis of the new product, and was enhanced to support Teams, Work Queues, Clinical Documentation, Pathways/Protocols, and much more.  At one point, out of curiosity, one of the HFHS data model team printed the entire logical model. It took up his entire wall.

We continued to expand EXR to be certified as a complete Inpatient and Outpatient EHR, and the Data Model was further enhanced to support some of the feature points, and encryption methods required for certification.

When we created Arcana, we enhanced the Data Model for all of our external sourced data tables and expanded them to fully accept any sourced data. This allows us to accept data from any combination of source systems, and be properly aggregated, preserving the original while at the same time being able to easily map it to any known Point-of-Truth (i.e. CPT, ICD and similar codesets).  With it, Arcana is able to assess patients realtime and have reaction situations for any number of use cases, including aiding in insurance reporting of HEDIS matching patients and their related data points.

The PhysBeeMD ADT Notification (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.