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 heart rate (pulse oximetry) measurements for a patient over a specified time range. It is useful in healthcare automation workflows where continuous or historical cardiac monitoring data is needed, such as remote patient monitoring, clinical research, or personalized health tracking.

For example, a healthcare provider could use this node to automatically fetch a patient's heart rate data recorded by a wearable device between two dates to analyze trends or detect anomalies without manual data entry.

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 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 to customize the request:
- Averaging Interval (Minutes) Time averaging interval in minutes (0-60) to smooth the heart rate data.
- 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 atrial fibrillation operation). Options: ECG (default), PPG.

Output

The node outputs an array of JSON objects representing the heart rate data points retrieved from the Cardiacsense API. Each object contains the measurement values and associated metadata unless the "Ignore Metadata" option is enabled, in which case the response is simplified.

If the node supports binary data output (not indicated here), it would typically represent raw device data or reports, but this node focuses on JSON-formatted vital sign data.

Dependencies

  • Requires an API key credential for authenticating with the Cardiacsense FHIR API.
  • The node makes HTTP GET requests to Cardiacsense endpoints using the provided credentials.
  • No additional external dependencies are required beyond standard n8n HTTP request capabilities.

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.
    • Using unsupported device types or options not matching the API specification can cause failures.
    • Network connectivity issues or invalid API tokens will prevent successful data retrieval.

  • Error Messages:

    • "Unknown operation: getHeartRate": Indicates the operation name is incorrect or not supported.
    • "Unknown patient management operation": Occurs if an unsupported operation under patient management resource is selected.
    • HTTP errors related to authorization usually mean the API token is invalid or expired.

  • Resolutions:

    • Verify all input parameters conform to expected formats.
    • Ensure the API key credential is correctly configured and active.
    • Check network access to the Cardiacsense API endpoints.
    • Use the "Ignore Metadata" option if metadata causes parsing issues.

Links and References

Discussion