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 focusing on heart rate measurements in this context. The "Get 12-Hour Average" operation under the "Heart Rate Data" resource fetches averaged heart rate data over a specified time range, allowing users to analyze patient heart rate trends efficiently.
Common scenarios where this node is beneficial include:
- Monitoring patient heart rate averages over half-day periods for clinical assessments.
- Aggregating heart rate data from wearable devices or manual entries to detect anomalies.
- Integrating cardiac data into broader health analytics workflows.
For example, a healthcare provider could use this node to pull a patient's average heart rate every 12 hours to monitor recovery progress after a cardiac event.
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 fields to customize the request: |
| - Averaging Interval (Minutes) | Time averaging interval in minutes (0-60) to specify how granular the averaging should be. |
| - Ignore Metadata | Boolean flag to return a simplified response without FHIR metadata if set to true. |
| - Device | Device type for measurement origin; options are: |
| • CardiacSense Watch | |
| • External Device | |
| • Manual by User | |
| - AF Source | Source for atrial fibrillation detection (only relevant for atrial fibrillation operations): |
| • ECG (Default) | |
| • PPG |
Output
The node outputs JSON data representing the averaged heart rate measurements within the specified time frame. The structure typically includes:
- Averaged heart rate values aggregated according to the specified interval.
- Timestamps corresponding to each averaged data point.
- Optional metadata unless ignored via the "Ignore Metadata" option.
If binary data were involved (not indicated here), it would represent raw device data or reports, but this node focuses on JSON-formatted numeric and timestamped data.
Dependencies
- Requires an active connection to the Cardiacsense FHIR API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- Network access to Cardiacsense endpoints (
baseUrlandactionsUrl) must be available.
Troubleshooting
Common Issues:
- Invalid or missing patient email can cause request failures.
- Incorrect date/time formats for start or end times may lead to errors or empty results.
- Specifying an unsupported averaging interval (outside 0-60 minutes) might cause unexpected behavior.
- Network or authentication issues with the Cardiacsense API will prevent data retrieval.
Error Messages:
"Unknown operation: get12HourAverage"— indicates the operation name is not recognized; ensure correct spelling and case."Unknown patient management operation"— appears if using patient management resource incorrectly.- HTTP errors related to authorization usually mean the API token is invalid or expired; reconfigure credentials.
- Date parsing errors suggest improper formatting; verify input matches expected patterns.
To resolve these, double-check all input parameters, ensure valid credentials, and confirm network connectivity.