Skip to content

Existing Specs and Data Models

As we embark on this Well Polaris FHIR Specification, we will be populating our Polaris MedPlum instance with significant amounts of EMR data. This is a large effort (both modelling and mapping), and is informed and constrained by many different existing data models and mappings.

Existing Specifications

Pan-Canadian Core FHIR Profile Set (CA Core+) - Pan Canadian Interoperability - InfoScribe

Preexisting Well FHIR Mappings

Preexisting FHIR mappings by Well products are valuable for 2 reasons:

  • Reuse of existing mappings can save effort (where it makes sense and where the existing maps align with standards).
  • Existing mappings that have been used in production indicate mappings that are possible from existing EMR data. As historic EMR data is largely unchangeable, is in existing schemas, and has significant volume, these insights can save considerable rework as we implement.

To this end, this page attempts to catalog the existing FHIR work that has been done across the Well organization so that it is easily accessible for both spec maintainers and implementers.

  • Shared FHIR Converter Library (source code, CPAR design) - being implemented for Polaris according to the spec. Intended to be compliant with the Well Polaris FHIR Spec.
  • OSCAR Pro R4 Converter Libraries (source code, sample output:) - per Michael Haddad "The mappings from the OSCAR Pro R4 Converter Libraries are going to be migrated over"
  • OCEAN (Cognisant) Cloud Connect (simplifier.net) - a specification implemented by several EMRs to extract a broad set of patient summary information. Battle hardened in production.

Existing Well Data Models