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 here on fetching calories-related activity data for a patient. It is useful in healthcare automation workflows where you want to analyze or monitor a patient's physical activity metrics over a specified time range.

A practical example would be a healthcare provider automatically pulling calorie expenditure data from a patient's wearable device records between two dates to assess their daily activity levels and adjust treatment plans accordingly.

Properties

Name Meaning
Patient Email Email address of the patient whose calories 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 (0-60) to aggregate data points.
- Ignore Metadata Boolean flag to return simplified response without FHIR metadata.
- Device Device type for measurement origin; options are: CardiacSense Watch, External Device, Manual by User.
- AF Source Source for atrial fibrillation detection; options are ECG (default) or PPG. (Not relevant for this operation.)

Output

The output is a JSON array containing the calories data retrieved from the Cardiacsense API for the specified patient and time range. Each item corresponds to a data point or aggregated data depending on the averaging interval set.

If the "Ignore Metadata" option is false, the response includes full FHIR metadata alongside the data values. If true, the response is simplified to exclude metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Cardiacsense FHIR API.
  • The node makes HTTP GET requests to the Cardiacsense API endpoints.
  • Proper configuration of the API base URL and authentication 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.
    • Setting an averaging interval outside the 0-60 minute range might cause unexpected results or API rejection.
    • Using unsupported device types or incorrect parameter names can lead to failed requests.

  • Error messages:

    • "Unknown operation: getCaloriesData": This indicates the operation name was not recognized; ensure the correct operation is selected.
    • "Unknown patient management operation": Occurs if a patient management operation is used instead of an activity data operation.
    • HTTP errors from the API (e.g., 401 Unauthorized) usually mean invalid or expired API credentials; re-authenticate or update credentials.

  • To resolve errors, verify all input parameters, especially required fields, and confirm API credentials are valid and have sufficient permissions.

Links and References

Discussion