Cardiacsense icon

Cardiacsense

Interact with Cardiacsense FHIR API for cardiac and health monitoring data
Join our community

Actions26

Overview

This node interacts with the Cardiacsense FHIR API to retrieve heart rate data and other cardiac-related health metrics. Specifically, for the Heart Rate Data resource and the Get 24-Hour Mean operation, it fetches averaged heart rate measurements over a specified time interval (typically 24 hours) for a given patient.

Common scenarios where this node is beneficial include:

  • Monitoring a patient's heart rate trends over a day to detect abnormalities or changes.
  • Integrating cardiac monitoring data into healthcare workflows or dashboards.
  • Automating alerts or reports based on daily heart rate averages.

For example, a healthcare provider could use this node to automatically pull a patient's 24-hour mean heart rate from their wearable device data and combine it with other clinical information for comprehensive patient monitoring.

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 retrieval in YYYY-MM-DD or YYYY-MM-DD HH:MM:SS format.
End Time End date/time for the data retrieval 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 heart rate data should be averaged.
- Ignore Metadata Boolean flag to return a simplified response without FHIR metadata.
- Device Device type for measurement origin. Options: CardiacSense Watch, External Device, Manual by User.
- AF Source Source for atrial fibrillation detection (only relevant for atrial fibrillation operation). Options: ECG (default), PPG.

Output

The node outputs JSON data representing the heart rate measurements averaged over the specified interval and time range. The structure typically includes:

  • Patient identification details (implicitly via the request).
  • Averaged heart rate values per defined intervals within the requested timeframe.
  • Optional metadata depending on the Ignore Metadata flag.

If the Ignore Metadata option is set to true, the output excludes detailed FHIR metadata, providing a simplified dataset focused on the core heart rate values.

The node does not output binary data.

Dependencies

  • Requires an active connection to the Cardiacsense FHIR API.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The node sends HTTP GET requests to Cardiacsense endpoints using the provided credentials.
  • No additional external dependencies beyond the Cardiacsense API and n8n's HTTP request capabilities.

Troubleshooting

  • Common Issues:

    • Invalid or missing patient email can cause the API to reject the request.
    • 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 failures if the API token is invalid or expired.

  • Error Messages:

    • "Unknown operation: get24HourMean" — indicates the operation name is incorrect or not supported; verify spelling and case.
    • "Unknown patient management operation" — occurs if the operation is used under the wrong resource.
    • HTTP 401 Unauthorized — check that the API token credential is correctly configured and valid.
    • HTTP 400 Bad Request — often due to malformed query parameters like dates or missing required fields.

  • Resolutions:

    • Ensure all required properties are filled with valid values.
    • Confirm the API token is current and has necessary permissions.
    • Use correct date/time formats as specified.
    • If ignoring metadata, verify downstream nodes can handle simplified data.

Links and References

Note: This summary is based solely on static analysis of the provided source code and property definitions.

Discussion