HCP Portal Integration
Overview
Through this integration clinical information entered manually by a RDCP "HCP portal" user is stored on the Data Lake for reporting and analytics purposes.
At this moment, only HbA1c information entered by the HCP manually from "HCP Portal" shall be shared with Data Lake.
Requirements
Scope
- The only source is the "HCP Portal"
- The only data received is related to HbA1c
- The data received are always "manual" entries
- There are 2 possible types of actions :
- CREATE - Creation of new HbA1c entry for a patient
- UPDATE - Updation of an existing HbA1c entry (the UUID of that entry has to be sent and the same should be used in the Observation.identifier so that the resource is updated using PUT).
- There are 2 possible units/formats in which we can receive the HbA1c data -
- % (used in NGSP protocol)
- mmol/mol. (Used in IFCC protocol)
Assumptions
- History of edited values are required to be stored in the RDS and not in the Data Lake
Use Cases
| Use Case | Summary | Comments |
|---|---|---|
| 1 | CREATE - Creation of new HbA1c entry for a patient | |
| 2 | UPDATE - Updation of an existing HbA1c entry | |
| 3 | HbA1c value entered in % | |
| 4 | HbA1c value entered in mmol/mol |
Data Points
| No. | Data Point | Description | FHIR Resource & Element | Remarks(sample Value) | FHIR Sample |
|---|---|---|---|---|---|
| 1 | uuid | Unique ID for HbA1C observation on HCP portal. The same UUID will be sent for updating an existing record. | Observation.identifier.value | 3cafaf5d-dbae-4e22-94f8-4e90deea6484 | Sample |
| 2 | patient_fhir_id | FHIR ID of the Patient related to HbA1C observation | Patient references in Observation.subject | jWd9d6p-iG5-62 | Sample |
| 3 | device_id | This is a sourceidentifier | MessageHeader.source.name, Device.model, DeviceComponent.identifier | jWd9d6p-iG5-62 | Sample |
| 4 | device_name | Detailed name of the source | MessageHeader.source.software | Roche Diabetes Care Platform HCP Web Portal | Sample |
| 5 | specification_version | version of the format specification (The version of the source (like HCP portal version) is not required) | MessageHeader.source.version, Device.version | 1.0.0 | Sample |
| 6 | data_point | Contains all information related to a particular data point. at the moment its only HbA1c. In future there could be more | - | ||
| 6a | system | The standard codesystem for the observation code (Sending the code from the source will help improve inter-operability) | Observation.code.coding.system | http://loinc.org/ | Sample |
| 6b | code | The standard code | Observation.code.coding.code | 4548-4 (for unit %), 59261-8 (for unit mmol/mol) | Sample |
| 6c | display | Display text for the standard code (could be optional) | Observation.code.coding.display | Hemoglobin A1c/Hemoglobin.total in Blood (for unit %) | Sample |
| 6d | unit | The unit in which the HbA1c value is measured | Observation.valueQuantity.unit | % | Sample |
| 6e | value | HbA1c value | Observation.valueQuantity.value | 7.5 (%) | Sample |
| 6f | measured_timestamp | Corresponds to the effective date of the HbA1c value. i.e. the date and time when the measurement was made | Observation.effectiveDateTime | 2012-04-23T18:25:43.511Z | Sample |
| 6g | registered_timestamp | This is the time when the doctor enters the data. In our current IG this is not required. But we can include this if it is necessary. (if required to store) | Observation.issued | 2012-04-24T20:25:10.511Z | Sample |
Solution Architecture
| Description | Link | Comments |
|---|---|---|
| HbA1c feature and data lake integration | https://confluence.rochedc.accentureanalytics.com/display/ARCGOV/HbA1c+feature+and+Data+Lake+integration |
High-Level Requirements
| Description | Link | Comments |
|---|---|---|
| Input data specification | https://confluence.rochedc.accentureanalytics.com/display/RD/Input+data+specification |
Profiles
List of profiles that are relevant to this application