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 heart rate data and other cardiac-related metrics for patients. Specifically, the "Get 10-Minute Mean" operation under the "Heart Rate Data" resource fetches averaged heart rate measurements over specified time intervals. This is useful in healthcare scenarios where clinicians or researchers need summarized heart rate trends rather than raw beat-to-beat data.
Practical examples include:
- Monitoring a patient's average heart rate during specific periods (e.g., overnight or during exercise).
- Aggregating heart rate data to detect anomalies or trends without dealing with large volumes of raw data.
- Integrating cardiac monitoring data into broader health analytics workflows.
Properties
| Name | Meaning |
|---|---|
| Patient Email | Email address of the patient whose heart rate 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). Defines how heart rate data is averaged over time. Default is 5 minutes. |
| - Ignore Metadata | Boolean flag to return simplified response without FHIR metadata. |
| - Device | Device type from which the measurement originated. Options: CardiacSense Watch, External Device, Manual by User. Default is CardiacSense Watch. |
| - AF Source | Source for atrial fibrillation detection. Options: ECG (default), PPG. Only relevant for atrial fibrillation operations. |
Output
The node outputs JSON data representing the requested heart rate information. The structure corresponds to the Cardiacsense API response, typically including:
- Averaged heart rate values over the specified intervals.
- Timestamps corresponding to each averaged data point.
- Optional metadata fields unless ignored via the "Ignore Metadata" option.
If the "Ignore Metadata" option is enabled, the output excludes FHIR metadata, providing a simplified dataset focused on core measurement values.
No binary data output is indicated for this operation.
Dependencies
- Requires an active API key credential for the Cardiacsense API.
- The node makes HTTP GET requests to Cardiacsense endpoints using the provided credentials.
- Proper configuration of the API base URL and authentication token is necessary within n8n credentials setup.
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 averaging intervals (outside 0-60 minutes) might lead to unexpected results.
- Network or authentication failures if the API key is invalid or expired.
Error Messages:
"Unknown operation: <operation>": Indicates that the specified operation is not supported by the node."Unknown patient management operation: <operation>": Occurs if an invalid patient management operation is selected.- HTTP errors related to authorization or connectivity will be surfaced as node execution errors.
Resolutions:
- Verify patient email correctness.
- Ensure date/time inputs follow the required format.
- Confirm API credentials are valid and have necessary permissions.
- Use the "Ignore Metadata" option if metadata causes parsing issues.
Links and References
- Cardiacsense API Documentation (example placeholder link)
- FHIR Standard Overview
- n8n Documentation on Creating Custom Nodes