Development of a module to manage all data relating to patients' cardiac health. This module will include the management of data such as heart rate, electrocardiograms, atrial fibrillation (AF) history, blood pressure, etc. To begin with, the module will focus on managing the patient's heart rate.
Features to be implemented
Creating heart rate data
Retrieving a patient's data
Route to retrieve a patient's heart rate data.
Data can be filtered using parameters (e.g. start date, end date, minimum/maximum heart rate, etc.).
Routes to be implemented
POST /v1/heart/rates
Description: Add heart rate data for a patient.
Body: JSON containing a table of heart rates and, if necessary, the patient's identifier (for healthcare professionals)
Description: Retrieve heart rate data from the connected patient or from a specific patient if patientId is provided.
Filter parameters (query params)
patientId?: Patient ID (optional, used by healthcare professionals).
startDate?: Filter start date.
endDate?: Filter end date.
minHeartRate?: Minimum heart rate.
maxHeartRate?: Maximum heart rate
Example of calls:
GET /v1/heart/rates?startDate=2024-06-01T00:00:00Z&endDate=2024-06-30T23:59:59Z&minHeartRate=60&maxHeartRate=120
GET /v1/heart/rates?patientId=12345&startDate=2024-06-01T00:00:00Z&endDate=2024-06-30T23:59:59Z&minHeartRate=60&maxHeartRate=120
Development of a module to manage all data relating to patients' cardiac health. This module will include the management of data such as heart rate, electrocardiograms, atrial fibrillation (AF) history, blood pressure, etc. To begin with, the module will focus on managing the patient's heart rate.
Features to be implemented
Routes to be implemented
/v1/heart/rates
/v1/heart/rates?patientId=123456
patientId
is provided.patientId?
: Patient ID (optional, used by healthcare professionals).startDate?
: Filter start date.endDate?
: Filter end date.minHeartRate?
: Minimum heart rate.maxHeartRate?
: Maximum heart rate