Actions26
- Activity Data Actions
- Advanced Metrics Actions
- Cardiac Conditions Actions
- Heart Rate Data Actions
- Patient Management Actions
- Vital Signs Actions
Overview
This node integrates with the Cardiacsense FHIR API to retrieve vital signs data, specifically blood pressure measurements for patients. It is designed to fetch time-series health data filtered by patient email and a specified time range. The node supports additional options such as averaging intervals, device type filtering, and simplified response formats.
Common scenarios where this node is beneficial include:
- Monitoring patient blood pressure trends over a specific period.
- Integrating cardiac vital sign data into healthcare workflows or dashboards.
- Automating alerts or reports based on blood pressure readings from wearable devices or manual entries.
For example, a healthcare provider could use this node to pull all blood pressure readings for a patient between January 1st and January 2nd, averaged over 5-minute intervals, originating from a specific device like the CardiacSense Watch.
Properties
| Name | Meaning |
|---|---|
| Patient Email | Email address of the patient whose blood pressure data is being requested. |
| Start Time | Start date/time for the data query in YYYY-MM-DD or YYYY-MM-DD HH:MM:SS format. |
| End Time | End date/time for the data query in YYYY-MM-DD or YYYY-MM-DD HH:MM:SS format. |
| Additional Options | Collection of optional parameters: |
| - Averaging Interval (Minutes) | Time averaging interval in minutes (0-60) to aggregate blood pressure readings. |
| - Ignore Metadata | Boolean flag to return a simplified response without FHIR metadata. |
| - Device | Device type filter for measurement origin; options are: |
| • CardiacSense Watch | |
| • External Device | |
| • Manual by User |
Note: The "AF Source" option is present but only relevant for atrial fibrillation detection operations, not for blood pressure retrieval.
Output
The node outputs an array of JSON objects representing blood pressure measurements within the specified time frame for the given patient. Each object corresponds to a single measurement or aggregated data point depending on the averaging interval.
If the "Ignore Metadata" option is false, the output includes full FHIR metadata associated with each measurement. If true, the output is simplified to contain only essential measurement data.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Cardiacsense API via an API key credential.
- The node expects valid credentials configured in n8n to authorize requests.
- Network access to the Cardiacsense API endpoints is necessary.
Troubleshooting
Common Issues:
- Invalid or missing patient email will cause the API request to fail.
- Incorrect date/time formats for start or end times may result in errors or empty responses.
- Using unsupported device types or invalid averaging intervals can lead to unexpected results.
- API authentication failures if the API key is expired or misconfigured.
Error Messages:
"Unknown operation: getBloodPressure": Indicates the operation name is incorrect or not supported."Unknown patient management operation": Occurs if the resource-operation combination is invalid.- HTTP errors related to authorization usually mean the API token is invalid or missing.
To resolve these issues:
- Verify that the patient email is correct and registered in the Cardiacsense system.
- Ensure date/time inputs follow the required format.
- Confirm the API key credential is properly set up and has necessary permissions.
- Use only supported device options and valid numeric values for averaging intervals.
Links and References
- Cardiacsense API Documentation
- FHIR Standard Overview
- n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)