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 detailed cardiac and health monitoring data. Specifically, for the Heart Rate Data resource with the Get Beat-to-Beat operation, it fetches beat-to-beat heart rate measurements for a specified patient within a given time range. This is useful in clinical or research settings where precise heart rate variability and rhythm analysis are needed.

Typical use cases include:

  • Monitoring patients remotely by retrieving continuous heart rate data.
  • Analyzing cardiac arrhythmias or other heart conditions using high-resolution heart rate signals.
  • Integrating cardiac data into broader health analytics workflows.

For example, a cardiologist could automate fetching a patient's beat-to-beat heart rate data over the last 24 hours to assess arrhythmia episodes or heart rate variability trends.

Properties

Name Meaning
Patient Email Email address of the patient whose heart rate data is being requested.
Start Time Start date/time for the data retrieval window, in YYYY-MM-DD or YYYY-MM-DD HH:MM:SS format.
End Time End date/time for the data retrieval window, 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 smooth the beat-to-beat data.
- Ignore Metadata Boolean flag to return a simplified response without FHIR metadata details.
- 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 operation). Options: ECG (default), PPG.

Output

The node outputs an array of JSON objects representing the retrieved beat-to-beat heart rate data points. Each object corresponds to a measurement or aggregated data point depending on the averaging interval specified.

  • The output JSON includes detailed heart rate values indexed by timestamp.
  • If "Ignore Metadata" is false, the response includes full FHIR metadata associated with each data point.
  • No binary data output is produced by this operation.

Example output snippet (simplified):

[
  {
    "timestamp": "2024-01-01T08:00:00Z",
    "heartRate": 72,
    "device": "cardiacsense_watch"
  },
  {
    "timestamp": "2024-01-01T08:01:00Z",
    "heartRate": 70,
    "device": "cardiacsense_watch"
  }
]

Dependencies

  • Requires an API key credential for authenticating with the Cardiacsense FHIR API.
  • The node uses HTTP GET requests to the Cardiacsense API 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

  • Invalid Date Format: Ensure that the start and end times are provided in YYYY-MM-DD or YYYY-MM-DD HH:MM:SS format. Incorrect formats may cause API errors.
  • Authentication Errors: Verify that the API key credential is valid and has not expired.
  • Unknown Operation Error: If the operation name does not match supported ones, the node will throw an error. Confirm the operation is set to "Get Beat-to-Beat".
  • Empty or Missing Data: If no data is returned, check that the patient email is correct and that data exists for the specified time range.
  • API Rate Limits: Excessive requests may be throttled by the Cardiacsense API; implement retry logic or reduce request frequency if needed.

Links and References

Discussion