CAD CARE Start a conversation

Healthcare data that can travel.

FHIR-based architecture for clinical exchange, application integration and research data flow.

Overview

What FHIR gives us

FHIR gives healthcare a resource model and an API surface that modern applications can actually build against. CAD CARE designs and implements FHIR-based architectures for clinical exchange, application integration and research data flow.

Model

  • FHIR R4
  • FHIR R5 where appropriate
  • Resources
  • Profiles
  • Extensions
  • Bundles

Interface

  • FHIR APIs
  • SMART on FHIR
  • Application integration
  • Subscriptions
  • Bulk data

Meaning

  • Terminology binding
  • ValueSets
  • CodeSystems
  • Patient identity
  • Consent

Where this sits

L1Experience
L2Application
L3Interoperability
L4Semantic
L5Data
L6Intelligence
L7Evidence
L8Transformation

Every CAD CARE technology capability is positioned against the same eight-layer stack, so it is always clear what a capability does and what it depends on.

FHIR architectureCLINICAL SYSTEMSFHIR APIsPatientEncounterObservationConditionMedicationDiagnosticReportImagingStudyDocumentReferenceHEALTHCARE DATA PLATFORMAI · ANALYTICS · RESEARCH

Scroll to see the full diagram →

Clinical systems through FHIR to analytics and research

On certification

Implementing FHIR does not imply certification of any kind. CAD CARE describes FHIR as an architectural capability. Formal conformance testing is carried out per engagement where a programme requires it.

Design a FHIR layer.

Resource model, profiles, terminology binding and API surface.

Start a conversation