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 cardiac and health monitoring data. Specifically, for the Cardiac Conditions resource and the Get Fluctuating Pulse Rate operation, it fetches pulse rate data that varies over a specified time interval for a given patient.

Common scenarios where this node is beneficial include:

  • Monitoring patients remotely by retrieving their pulse rate fluctuations over time.
  • Analyzing cardiac arrhythmia or irregular heartbeats by examining pulse rate variability.
  • Integrating cardiac health data into broader healthcare workflows or dashboards.

For example, a healthcare provider could use this node to pull fluctuating pulse rate data from a patient's wearable device between two dates to assess cardiac health trends.

Properties

Name Meaning
Patient Email Email address of the patient whose data is being retrieved.
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 to customize the request:
- Averaging Interval (Minutes) Time averaging interval in minutes (0-60) to smooth the pulse rate data.
- 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 other operations, not this one). Options: ECG (Default), PPG.

Output

The node outputs JSON data representing the fluctuating pulse rate measurements for the specified patient and time range. The structure includes:

  • Time-stamped pulse rate values, potentially averaged over the specified interval.
  • Depending on the Ignore Metadata option, the output may include or exclude detailed FHIR metadata.
  • The data reflects measurements originating from the selected device type.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Cardiacsense FHIR API via an API key credential.
  • The node expects valid credentials configured in n8n to authenticate requests.
  • Network access to the Cardiacsense API endpoints is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing patient email will cause the API to reject the request.
    • Incorrect date/time formats for start or end times can lead to errors or empty results.
    • Specifying an unsupported device type or averaging interval outside 0-60 minutes may cause unexpected behavior.
    • Network or authentication failures if the API token is invalid or expired.

  • Error Messages:

    • "Unknown operation": Occurs if the operation name does not match supported ones; ensure "Get Fluctuating Pulse Rate" is correctly selected.
    • "Unknown patient management operation": Not applicable here but indicates misuse of patient management operations.
    • HTTP errors related to authorization indicate issues with the API key credential setup.

  • Resolution Tips:

    • Verify all required fields are filled with correct formats.
    • Check API credentials and refresh tokens if needed.
    • Use the Ignore Metadata option to simplify output if parsing complex FHIR metadata is problematic.

Links and References

Discussion