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 advanced cardiovascular and monitoring metrics for patients. Specifically, the "Get Night RRV Data" operation fetches heart rate variability data recorded overnight, which can be used to assess autonomic nervous system function and cardiac health during sleep.

Common scenarios where this node is beneficial include:

  • Monitoring patients remotely for cardiac health trends.
  • Analyzing night-time heart rate variability to detect potential arrhythmias or stress responses.
  • Integrating advanced cardiac metrics into broader health analytics workflows.

Practical example: A healthcare provider could use this node to automatically pull a patient's night RRV data over a specified date range to evaluate changes in cardiac autonomic regulation after a treatment intervention.

Properties

Name Meaning
Patient Email Email address of the patient whose 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 for the returned data (0-60).
- Ignore Metadata Boolean flag to return simplified response without FHIR metadata.
- 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 AF-related operations). Options: ECG (default), PPG.

Output

The node outputs JSON data representing the requested advanced metric—in this case, night RRV data—structured according to the Cardiacsense FHIR API response. The output includes time-series measurements of heart rate variability over the specified period, optionally averaged per the provided interval.

If the "Ignore Metadata" option is set, the output excludes detailed FHIR metadata, providing a simplified dataset focused on the core measurement values.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Cardiacsense FHIR API.
  • The node expects proper configuration of the API base URL and authorization token within the credential.
  • Network access to the Cardiacsense API endpoints is necessary.

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 unsupported devices or averaging intervals outside 0-60 minutes may lead to unexpected results.
    • API authentication failures if the API key/token is invalid or expired.

  • Error Messages:

    • "Unknown operation: <operation>": Indicates that the specified operation is not supported by the node; verify the operation name.
    • "Unknown patient management operation: <operation>": Occurs if an unsupported patient management operation is selected.
    • HTTP errors from the API (e.g., 401 Unauthorized) suggest issues with credentials or permissions.

  • Resolutions:

    • Ensure all required properties are correctly filled with valid values.
    • Confirm the API key credential is up-to-date and has necessary permissions.
    • Validate date/time inputs conform to expected formats.
    • Use the "Ignore Metadata" option if FHIR metadata complicates downstream processing.

Links and References

Discussion