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.