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 including blood glucose measurements for patients. It is designed to fetch time-series health data filtered by patient email and a specified time range. The "Get Blood Glucose" operation under the "Vital Signs" resource allows users to obtain detailed or simplified blood glucose readings collected from various devices.

Common scenarios where this node is beneficial include:

  • Monitoring diabetic patients' blood glucose levels over a specific period.
  • Integrating continuous glucose monitoring data into automated workflows.
  • Aggregating and analyzing patient vital signs for clinical decision support.

Practical example: A healthcare provider can use this node to automatically pull a patient's blood glucose data from Cardiacsense devices between two dates, then trigger alerts if abnormal values are detected.

Properties

Name Meaning
Patient Email Email address of the patient whose blood glucose data is being retrieved.
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 measurements.
- Ignore Metadata Boolean flag to return a simplified response without FHIR metadata.
- Device Device type for measurement origin. Options: CardiacSense Watch, External Device, Manual by User.
- AF Source Source for atrial fibrillation detection (only relevant for other operations, not this one).

Output

The output is a JSON array containing blood glucose measurement records matching the query parameters. Each item corresponds to a single measurement or an aggregated value depending on the averaging interval specified.

  • If Ignore Metadata is false, each record includes full FHIR metadata describing the measurement context.
  • If Ignore Metadata is true, the response is simplified to essential measurement data only.

No binary data output is produced by this operation.

Dependencies

  • Requires an active API key credential for the Cardiacsense FHIR API.
  • The node makes authenticated HTTP GET requests to Cardiacsense endpoints.
  • Proper configuration of the API base URL and authorization token is necessary within n8n credentials.

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 an unsupported device type or averaging interval outside 0-60 minutes could lead to unexpected results.
    • Network or authentication failures will prevent data retrieval.

  • Error messages:

    • "Unknown operation: getBloodGlucose": Indicates the operation name was not recognized; ensure correct spelling and case.
    • "Unknown patient management operation": Not applicable here but indicates misuse of resource-operation combinations.
    • HTTP 401 Unauthorized: Check that the API key credential is valid and has not expired.
    • HTTP 400 Bad Request: Verify all required parameters are provided and correctly formatted.

To resolve errors, verify input parameters, ensure valid credentials, and confirm network connectivity.

Links and References

Discussion