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 vital signs data, specifically oxygen saturation measurements for patients. It is designed to fetch time-series health data filtered by patient email and a specified time range. The node supports additional options such as averaging intervals, device type filtering, and simplified response formats.

Common scenarios:

  • Monitoring a patient's oxygen saturation over a specific period to assess respiratory health.
  • Aggregating oxygen saturation data averaged over configurable time intervals for trend analysis.
  • Filtering data by measurement device to compare readings from different sources.
  • Simplifying responses by excluding metadata for easier downstream processing.

Practical example:
A healthcare provider wants to analyze oxygen saturation levels of a patient between January 1st and January 2nd, 2024, using data collected from a CardiacSense Watch, averaged every 5 minutes, and without extra metadata cluttering the output.

Properties

Name Meaning
Patient Email Email address of the patient whose oxygen saturation 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 aggregate oxygen saturation data.
- Ignore Metadata Boolean flag to return a simplified response without FHIR metadata.
- Device Device type filter for measurement origin; options are: CardiacSense Watch, External Device, Manual by User.
- AF Source (Not applicable for this operation) Source for atrial fibrillation detection; options: ECG (Default), PPG.

Output

The node outputs an array of JSON objects representing oxygen saturation measurements retrieved from the Cardiacsense API. Each object corresponds to a data point within the specified time range and may include:

  • Measurement values (oxygen saturation percentages).
  • Timestamps indicating when each measurement was taken.
  • Optional metadata depending on the Ignore Metadata option.

If binary data were involved (not in this operation), it would represent raw device data or attachments, but here the output is purely JSON-formatted health metrics.

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 via credentials.
  • 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 can lead to errors or empty results.
    • Using unsupported device types or invalid averaging intervals may result in API rejections.
    • Network connectivity problems or expired API tokens will prevent successful data retrieval.

  • Error messages:

    • "Unknown operation: getOxygenSaturation": Indicates the operation name is not recognized; verify spelling and case.
    • "Unknown patient management operation": Occurs if the resource-operation combination is incorrect.
    • HTTP 401 Unauthorized: Check that the API key credential is valid and has not expired.
    • HTTP 400 Bad Request: Usually due to malformed parameters like dates or unsupported options.

  • Resolutions:

    • Ensure all required fields are correctly filled and formatted.
    • Validate API credentials and refresh if needed.
    • Review device and averaging interval options for correctness.
    • Use the Ignore Metadata option to simplify output if parsing complex FHIR metadata causes issues.

Links and References

Discussion