How to read this guide

Data scope and Data Semantics

This interoperability guide enables a small subset of all data managed by Roche Diabetes Care Digital product portfolio, selected due to its business relevance and medical value. This scope is disclosed as part of this guides Data catalog.

Implementation guide structure

This Guide has the following sections:

• Home: The home page provides the introduction, purpose and design strategy of this guide.
• Guidance: These pages provide guidance for use of FHIR in the context Roche Diabetic Care.
• Profiles: Index of FHIR profiles (including extensions) supported in Roche Diabetes Care Interoperability layer that provide formal definitions, detailed descriptions, usage, and examples. Profiles are presented in several forms:
  • Rendered view: A dynamic and clickable tree view structure of the profile. Contains detailed descriptions shown when hovering over an element.
    • Snapshot: a fully calculated form of the structure. It contains the rendering of profile constraints on top of all its base resource definitions. Please note that '0..0' elements are not shown in the snapshot rendering.
    • Differential: this describes only the differences that the profile makes relative to the structure definition (FHIR resource) they constrain.
    • Hybrid: a hybrid view of the snapshot and differential views. The base definition elements which are not constrained by the profile are shown greyed out.
    • Show common: reveals all resource common elements such as id and meta.
  • Detailed Descriptions: This shows the complete dictionary with all details.
  • XML and JSON view: The raw XML and JSON format of the profile.
  • Further information from HL7 relating to profiling is available on the HL7 FHIR Profiling page.
  • Resource examples are rendered in the following formats:
    • JSON: a rendering in JSON format.
    • XML: a rendering in XML format.
    • Tree: an interactive tree view.
    • Table: a tabular view of the example.
• Terminology: Lists the supported CodeSystems and ValueSets and some provides additional guidance regarding these type of resources. Value set specifies a set of codes defined by code systems that can be used in a specific context.
• Implementations: Technical details about the FHIR Server variants that implements this IG. Each implementation may serve different purposes and as such, a subset of the datapoints and profiles may be implemented.
• Artifacts Summary: These pages provide lists and overview pages per category for all relevant artifacts defined in this guide.