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 Atrial Fibrillation operation, it fetches atrial fibrillation detection data for a specified patient within a given time range.

Typical use cases include:

  • Monitoring patients remotely for episodes of atrial fibrillation.
  • Integrating cardiac arrhythmia data into healthcare workflows or dashboards.
  • Analyzing atrial fibrillation trends over time for clinical decision support.

For example, a healthcare provider could use this node to automatically pull atrial fibrillation events detected by wearable devices or manual entries, filtered by device type and detection source, to review patient heart rhythm status.

Properties

Name Meaning
Patient Email Email address of the patient whose atrial fibrillation data is 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 data points.
- Ignore Metadata Boolean flag to return simplified response without FHIR metadata.
- Device Device type where measurement originated. Options: CardiacSense Watch, External Device, Manual by User.
- AF Source Source for atrial fibrillation detection. Options: ECG (default), PPG (photoplethysmography).

Output

The node outputs JSON data representing atrial fibrillation detection records for the specified patient and time range. The structure corresponds to the Cardiacsense API response, which may include:

  • Timestamps of detected atrial fibrillation events.
  • Measurement values aggregated according to the averaging interval.
  • Device and source metadata unless ignored.
  • Other relevant cardiac condition details as provided by the API.

If the "Ignore Metadata" option is enabled, the output excludes FHIR metadata for a simplified dataset.

No binary data output is produced by this operation.

Dependencies

  • Requires an active API key credential for the Cardiacsense API.
  • The node makes authenticated HTTP GET requests to Cardiacsense endpoints.
  • Proper configuration of the API base URL and authorization token is necessary.
  • Date/time inputs must be correctly formatted as per the API requirements.

Troubleshooting

  • Common Issues:

    • Invalid or missing patient email will cause request failures.
    • Incorrect date/time formats can lead to API errors or empty results.
    • Using unsupported device or AF source options may result in unexpected responses.
    • Network or authentication issues with the Cardiacsense API will cause errors.

  • Error Messages:

    • "Unknown operation: getAtrialFibrillation": Indicates the operation name was not recognized; ensure correct spelling and casing.
    • "Unknown patient management operation": Occurs if patient management operations are used incorrectly.
    • HTTP errors related to authorization usually mean the API token is invalid or expired.

  • Resolutions:

    • Verify all required fields are filled and properly formatted.
    • Check API credentials and refresh tokens if needed.
    • Use the "Ignore Metadata" option to simplify output if parsing complex FHIR metadata is problematic.
    • Enable "Continue On Fail" to handle partial failures gracefully during batch processing.

Links and References

Discussion