RDC Interoperability Guide
1.0.0

Observational data

Observational data administration is structured around 3 key Observation profiles that are generated by a Device and have a Patient subject.

ProfileDescription
Device Instance

Represents a specific instance of a Device, linking it to its corresponding Device Model with details such as serial number and configuration.

Observation BG

A clinical observation capturing a patient’s blood glucose level. This profile serves as a parent observation for related profiles, such as carbohydrate intake or Estimated Weight Mean (EWM), which provide additional context. Blood glucose measurements can be recorded by the patient or directly by a device.

Observation CGM

Defines observations specific to continuous glucose monitoring (CGM), capturing glucose levels over time to support ongoing clinical and patient monitoring.

Observation

A profile designed to capture additional context related to diabetic care, such as carbohydrate intake, Estimated Weight Mean (EWM), and similar details. This version focuses exclusively on estimated carbohydrate intake, with potential future expansions to broaden its scope.

Patient

A stripped-down patient profile containing no elements except for common resource metadata, such as the .id.

Data model overview

Data Flow for write action

The data flow for administering observational data follows these steps:

  1. Device administration flow (if not arleady available)
  2. Create RdcPatient instance (if not arleady available)
  3. Create RdcObservation instance(s)
  4. Create RdcObservationBG and/or RdcObservationCGM instances, referencing the relevant RdcDeviceInstance, RdcPatient and RdcObservation (using the .hasMember reference)