Vantis Patient Data Overview

Home

Vantis enables patients to request their data in a JSON format in accordance with requirements for 'Digitale Gesundheitsanwendungen (DiGA)': the HL7® FHIR® format.

In this format, general patient data (e.g. name, birth date, see https://simplifier.net/coreprofilesstu3/patient) are accessible on the top level. Measurement data (e.g. sensor data) is available within so-called extensions. Each extension contains a serialized collection of individual data points such as blood pressure measurements.

Extension

The following data types are provided in the mentioned extensions

DataChunks

contain measurement data collected from sensors, such as blood pressure (BP) or heart rage (HR) measurements.

field	description
user_id	Owner of the data
recorded_time	Transmission time
start_time	First entry in content
end_time	Last entry in content
data_type	Describes the type of content, e.g. BP for blood pressure measurement.
content	Contains measurement, json

MedicationReminders

contain information about medication reminders that were once scheduled, and which comprise the evolution of the medication plan.

field	description
user_id	Owner of the data
reminder_time	time when this reminder should trigger, can be None
every	A number describing how many skips should be performed before event: e.g. every day
medication	A reference to a medication
dose	Information regarding dosis
usage_information	Information and Settings collected to perform the therapy
reason	Description of the reason to take the medication, could be Heart related
scheduling_type	Daily, every second day, etc.
time_classification	e.g. morning, night, ...
inactive	set to true if removed from the plan
creation_time	auto set now
deactivation_time	set when inactive is set to true

PerformedActivities

contain data regarding performed activities, such as sport activities.

field	description
user_id	Owner of the data
activity	Reference to an activity performed in the App
schedule_date	Date this activity was scheduled by the app
event_type	type of performed action, e.g. Done
event_time	datetime when the activity was performed
additional_information	contains the version of the activity, or information specified by the user via e.g. multiple choice

ScheduledActivityCollections

contain data about scheduled activity collections (e.g. sport programs consisting of several exercises).

field	description
user_id	Owner of the data
activity_collection	Id of a collection of activities that was scheduled for the user
start_date	Start date of the collection
end_date	End date of the collection

ScheduledActivities

contain data about scheduled activities (such as individual sport activities).

field	description
user_id	Owner of the data
activity	Reference to an activity performed in the App
schedule_date	Date this activity was scheduled by the app
user_specific_title_list	Title for this activity and user
user_specific_categorization_text	Categorization for this activity and user
user_specific_max_completions	Number of required completion for this activity and user

FoodTrackingEvent

contain data tracked via the Nutrition Tracker.

field	description
user_id	Owner of the data
food_items	List of food items
event_time	datetime when the tracking was performed

MedicationTrackingEvent

contain data tracked via the Medication Tracker.

field	description
user_id	Owner of the data
event_time	datetime when the tracking was performed
tracked_medication	list of tracked medication
skipped_medication	list of medication marked as skipped

SymptomTrackingEvent

contain data regarding tracked Symptoms.

field	description
user_id	Owner of the data
symptom	reference to one of the selectable symptoms
event_time	datetime when the tracking was performed
doctor_required	Selection, if doctor or call was required, etc.
description	Free text provided by the user

UserInformation

contain the last state of personal information provided by the user.

field	description
user_id	Owner of the data
profile	Profile information stated by the user
diagnosis	Diagnosis information stated by the user
blood_work	Blood work information stated by the user
body_measures	Body measure information stated by the user
onboarding	Onboarding question answers
scheduling_settings	Scheduling information
app_settings	General properties
devices	Device information

UserActionRecord

contain app usage data.

field	description
user_id	Owner of the data
event_time	datetime when the tracking was performed
action	string describing what happened

UserTrackings

contain updates that the user made to their personal information (contained in the UserInformation object).

field	description
user_id	Owner of the data
created	datetime when the tracking was performed
smoking_state	Smoking state of the user
ldl_cholesterol_in_mm_dl	Updated entry for LDL
hdl_cholesterol_in_mm_dl	Updated entry for HDL
weight_in_kg	Updated weight
therapy_progress_offset	Updated delay
sport_forbidden_until	Updated sport forbidden date
exercise_path	Update exercise level
course_preference	Updated course preference

Example

For reference a minimal, exemplary JSON export is shown below. It contains a single extension, containing a single DataChunk, which in turn contains a single blood pressure measurement:

		{'birthDate': '1960-01-01',
		 'gender': 'female',
		 'identifier': [{'value': 'User_1'}],
		 'name': [{'text': 'Test User'}],
		 'resourceType': 'Patient',
		 'text': {'div': '<!-- This is an exported user -->', 'status': 'generated'}
		 'extension': [{'url': 'https://staging.vantis-app.com/content_media/patient_profile.html', 'valueString': '[{\"model\": \"monitoring.datachunk\", \"pk\": 48476, \"fields\": {\"user_id\": 146, \"recorded_time\": \"2021-08-10T05:13:47.082Z\", \"start_time\": \"2021-08-10T05:13:36Z\", \"end_time\": \"2021-08-10T05:13:36Z\", \"data_type\": \"BP\", \"content\": [{\"systolic\": 107, \"diastolic\": 79, \"heartRate\": 55, \"timestamp\": \"2021-08-10T05:13:36.000Z\", \"dataSource\": \"OMRON\", \"irregularHeartBeat\": false, \"incorrectMeasurement\": false}]}}]']
		    }]}