Implementation guide of the digital health application "BabyCare - Gesund & Schwanger" by FBE Forschung Beratung Evaluation GmbH
Validity: BabyCare App as of version 3.1.4
1. Introduction
1.1 Document history
| Version | Date | Authors |
|---|---|---|
| 1.0 | 10.02.2022 | SNK, JT |
1.2 Goal
This document serves to describe the interoperability of the digital health application "BabyCare-Gesund&Schwanger". With this document, the manufacturer FBE Forschung Beratung Evaluation GmbH discloses the interoperable format and coding used as a compilation over several HL7 FHIR profile definitions.
The standards and profiles used to establish the interoperability of the digital health application are published in the FHIR Registry Simplifier and the vesta interoperability directory and can be used without discrimination. In addition to this interoperable export format as FHIR, another export format as JSON is also defined and available in the vesta information portal.
According to Section 388 (4) of the Fifth Book of the German Social Code (SGB V), providers of an electronic health care application according to Section 306 (1) Sentence 2 Number 2 SGB V or of an electronic application that is fully or partially financed by funds of the statutory health insurance must submit an application according to Section 388 (1) SGB V. Since no suitable interface is available in the interoperability directory pursuant to Section 385 SGB V at the time the document is created, the digital health application supports another disclosed and documented interface which is either listed in the interoperability directory pursuant to Section 385 SGB V or for which a corresponding application has been submitted by the manufacturer.
1.3 Scope
This data export standard applies to the digital health application "BabyCare - Gesund & Schwanger" by FBE Forschung Beratung Evaluation GmbH.
2. FHIR format (JSON)
The data is encoded in the FHIR standard (HL7 FHIR R4). This established standard, which is internationally recognized in the healthcare industry, enables a defined and at the same time flexible output of the most diverse types of data.
The output of FHIR-compatible data is in JSON format. JSON is an internationally recognized interface and semantics standard (RFC 8259, ECMA-404 as well as ISO/IEC 21778:2017).
The individual entries in the exported FHIR bundle are listed and explained below.
An overview of the FHIR resources used is also available in the FHIR Registry Simplifier at https://simplifier.net/fbebabycareapp/.
2.1. Basic structure of a bundle
The bundle represents the current state of the app at the time of export. It contains any collection of Quicktest and Analysis entries.
| Name | Type | Description |
|---|---|---|
| identifier | string | A persistent identifier for the bundle |
| type | code | Indicates the purpose of this bundle |
| timestamp | timestamp | The date/time that the bundle was assembled |
| quicktest | array of objects | Contains several observations from the app's quicktests |
| analysis | array of objects | Contains several observations from the app's detailed analysis |
2.2 Quicktest Entry (Observation)
Inputs from the "Tests" app area are serialized here as Observation.
| Name | Type | Description |
|---|---|---|
| fullUrl | uri | URI for resource (URI for UUID/OID) |
| resource | object | Resource that represents user given answer |
| resource.identifier | string | Identifier that is used in the app |
| resource.resourceType | code | „Observation" |
| resource.status | code | Status of the observation: preliminary | final |
| resource.interpretation | object | Further information to help interpret the values |
| resource.interpretation.text | string | The actual question the values belong to |
| resource.value | object | None-one or multiple values the user reported |
| resource.value.valueString | string (optional) | Actual value in string format: „Rauche derzeit" |
| resource.value.valueInteger | Integer (optional) | Actual value in integer format: 4 |
| resource.values.value.valueDecimal | decimal (optional) | Actual value in decimal format: 1,5 |
2.3 Analysis (Observation)
Inputs from the „Ausführliche Analyse" (Detailed Analysis) app area are serialized here as Observation.
| Name | Type | Description |
|---|---|---|
| fullUrl | uri | URI for resource (URI for UUID/OID) |
| resource | object | Resource that represents user given answer |
| resource.identifier | string | Identifier that is used in the app |
| resource.resourceType | code | „Observation" |
| resource.status | code | Status of the observation: preliminary | final |
| resource.interpretation | object | Further information to help interpret the values |
| resource.interpretation.text | string | The actual question the values belong to |
| resource.values | array of objects | Collection of value entries |
| resource.values.value | object | None, one or multiple values the user reported |
| resource.values.value.valueString | string (optional) | Actual value in string format: „Bin schwanger" |
| resource.values.value.valueInteger | integer (optional) | Actual value in integer format: 7 |
| resource.values.value.valueDecimal | decimal (optional) | Actual value in decimal format: 1,5 |