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

Common scenarios where this node is beneficial include:

  • Monitoring patient body temperature trends over a period for clinical or remote health monitoring.
  • Integrating body temperature data into broader health analytics workflows.
  • Automating alerts or reports based on temperature changes detected in patient data.

Practical example: A healthcare provider can use this node to pull body temperature data recorded by a cardiac watch device for a specific patient between two dates, optionally averaging the data over intervals or simplifying the response format for easier processing.

Properties

Name Meaning
Patient Email Email address of the patient whose body temperature 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 temperature data points.
- Ignore Metadata Boolean flag to return a 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 other operations, not for body temperature). Options: ECG (default), PPG.

Output

The node outputs an array of JSON objects representing the body temperature data retrieved from the Cardiacsense API. Each object corresponds to a measurement or aggregated data point within the specified time range.

  • If "Ignore Metadata" is false or unset, the output includes full FHIR metadata associated with each measurement.
  • If "Ignore Metadata" is true, the output is simplified to contain only essential temperature values and timestamps.
  • The output does not include binary data.

Example output structure (simplified):

[
  {
    "timestamp": "2024-01-01T08:00:00Z",
    "temperature": 36.7,
    "device": "cardiacsense_watch",
    "unit": "Celsius"
  },
  ...
]

Dependencies

  • Requires an API key credential for authenticating with the Cardiacsense FHIR API.
  • The node expects the base URL and authorization token to be configured via credentials.
  • No additional external dependencies beyond HTTP access to the Cardiacsense API.

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 invalid averaging intervals could lead to unexpected results.
    • Network or authentication failures if the API key is invalid or expired.

  • Error messages:

    • "Unknown operation: getBodyTemperature": Indicates the operation name is incorrect or not supported.
    • "Unknown patient management operation": Occurs if the resource-operation combination is mismatched.
    • HTTP errors from the API (e.g., 401 Unauthorized) suggest credential issues.

  • Resolutions:

    • Verify that the patient email is correct and registered in the Cardiacsense system.
    • Ensure date/time inputs follow the required format.
    • Confirm the API key credential is valid and has necessary permissions.
    • Use the "Ignore Metadata" option to simplify output if parsing complex FHIR metadata causes issues.

Links and References

Discussion