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 cardiac and health monitoring data. Specifically, for the Heart Rate Data resource with the Get 10-Hour Mean operation, it fetches averaged heart rate measurements over a specified time interval (defaulting to a 10-hour window). This is useful in clinical or personal health monitoring scenarios where understanding average heart rate trends over extended periods helps assess cardiovascular health or detect anomalies.
Practical examples include:
- Monitoring a patient's heart rate averages during sleep or rest periods.
- Comparing heart rate trends before and after medication or lifestyle changes.
- Aggregating data from specific devices like the CardiacSense Watch or external monitors.
Properties
| Name | Meaning |
|---|---|
| Patient Email | Email address of the patient whose heart rate data is being retrieved. |
| 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 specify how data should be averaged within the period. Default is 5 minutes. |
| - Ignore Metadata | Boolean flag to return a simplified response without FHIR metadata if set to true. |
| - Device | Device type for measurement origin. Options: CardiacSense Watch, External Device, Manual by User. |
Note: The "AF Source" option is not applicable for this operation and thus omitted here.
Output
The node outputs JSON data representing the averaged heart rate measurements over the requested time interval. The structure typically includes:
- Timestamped heart rate values averaged according to the specified interval.
- If metadata is not ignored, additional FHIR metadata related to the measurements.
- The output is an array of objects, each corresponding to a time segment's averaged heart rate data.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Cardiacsense FHIR API.
- Needs an API authentication token credential configured in n8n.
- The node sends HTTP GET requests with appropriate query parameters including patient email, time range, device type, and averaging interval.
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.
- Specifying an averaging interval outside the 0-60 minute range might lead to unexpected results or API rejection.
- Network or authentication failures due to invalid or expired API tokens.
Error Messages:
"Unknown operation: get10HourMean": Indicates the operation name was not recognized; ensure correct operation selection."Unknown patient management operation": Not relevant here but indicates misuse of operations under different resources.- HTTP errors from the API (e.g., 401 Unauthorized) suggest issues with credentials.
Resolutions:
- Verify patient email correctness.
- Use valid ISO date/time strings for start and end times.
- Ensure the API key/token is valid and has necessary permissions.
- Adjust averaging interval within allowed limits.
Links and References
- Cardiacsense API Documentation (hypothetical link for reference)
- FHIR Standard Overview
- n8n Documentation on Creating Custom Nodes