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 focusing on activity-related metrics such as sleep data. The "Get Sleep Data" operation under the "Activity Data" resource allows users to fetch detailed sleep information for a specified patient within a given time range.

Common scenarios where this node is beneficial include:

  • Healthcare providers monitoring patients' sleep patterns remotely.
  • Researchers collecting sleep data for clinical studies.
  • Wellness applications integrating sleep insights into user profiles.

For example, a healthcare provider can input a patient's email and specify a date range to obtain their sleep data averaged over 5-minute intervals from a specific device like the CardiacSense Watch.

Properties

Name Meaning
Patient Email Email address of the patient whose sleep 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 a 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 atrial fibrillation operations). Options: ECG (default), PPG.

Output

The node outputs an array of JSON objects representing the sleep data retrieved from the Cardiacsense API. Each object corresponds to a data point or record within the specified time range and includes fields depending on the request parameters and device source.

If the "Ignore Metadata" option is set to true, the output excludes FHIR metadata, providing a simplified data structure focused on core sleep metrics.

No binary data output is indicated for 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 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 may result in errors or empty responses.
    • Specifying unsupported devices or invalid averaging intervals could lead to unexpected results.
    • API authentication failures if the API key/token is invalid or expired.

  • Error Messages:

    • "Unknown operation: getSleepData": Indicates the operation name might be misspelled or not supported.
    • "Unknown patient management operation": Occurs if the resource-operation combination is incorrect.
    • HTTP errors related to authorization typically mean the API token is invalid or missing.

To resolve these issues:

  • Verify all required properties are correctly filled.
  • Ensure date/time strings follow the expected format.
  • Confirm that the API credentials are valid and have sufficient permissions.
  • Use the "Ignore Metadata" option to simplify output if parsing complex FHIR metadata is problematic.

Links and References

Discussion