Cardiacsense icon

Cardiacsense

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

Actions26

Overview

This node integrates with the Cardiacsense FHIR API to retrieve heart rate data and other cardiac-related health metrics. Specifically, for the "Heart Rate Data" resource with the "Get 1-Hour Average" operation, it fetches averaged heart rate measurements over a specified time interval for a given patient.

Common scenarios where this node is beneficial include:

  • Monitoring a patient's heart rate trends over specific periods.
  • Aggregating heart rate data into averages for easier analysis.
  • Integrating cardiac monitoring data into broader healthcare workflows or dashboards.

Practical example:

  • A healthcare provider wants to analyze a patient's average heart rate every 5 minutes between January 1st and January 2nd, 2024, using data collected from a CardiacSense watch.

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) to specify how heart rate data should be averaged.
- Ignore Metadata Boolean flag to return a simplified response without FHIR metadata if set to true.
- Device Device type from which the measurement originated. 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 intervals within the requested time range. The structure corresponds to the Cardiacsense API response, potentially including detailed FHIR metadata unless the "Ignore Metadata" option is enabled.

If the "Ignore Metadata" option is set to true, the output will be a simplified JSON format focusing on the core heart rate values without additional metadata.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Cardiacsense FHIR API.
  • Requires an API authentication token credential configured in n8n.
  • Network access to Cardiacsense endpoints as defined by the credentials.
  • Properly formatted input dates and valid patient email addresses.

Troubleshooting

  • Common issues:

    • Invalid or missing patient email can cause request failures.
    • Incorrect date/time formats may lead to errors or empty results.
    • Using an unsupported averaging interval (outside 0-60 minutes) might cause unexpected behavior.
    • Missing or expired API authentication token will result in authorization errors.

  • Error messages:

    • "Unknown operation: <operation>": Indicates that the specified operation is not supported; verify the operation name.
    • "Unknown patient management operation: <operation>": Occurs if an invalid patient management operation is selected.
    • HTTP errors related to authorization usually mean the API token is invalid or expired.
    • Network or timeout errors suggest connectivity issues with the Cardiacsense API.

To resolve these:

  • Double-check all input parameters for correctness.
  • Ensure the API token credential is valid and has necessary permissions.
  • Confirm network connectivity to the Cardiacsense service.
  • Use the "Ignore Metadata" option if you want simpler output and avoid parsing complex FHIR structures.

Links and References

Discussion