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

Common scenarios where this node is beneficial include:

  • Monitoring patient body weight trends over time for clinical or wellness purposes.
  • Integrating body weight data into broader health analytics workflows.
  • Automating retrieval of patient vital signs for remote monitoring or telehealth applications.

For example, a healthcare provider could use this node to automatically pull body weight data recorded by a cardiac watch device between two dates to assess fluid retention in heart failure patients.

Properties

Name Meaning
Patient Email Email address of the patient whose body weight 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 refine the data request:
- 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 details.
- Device Device type origin of the measurement; options are: CardiacSense Watch, External Device, Manual by User.
- AF Source (Not applicable for Get Body Weight) Source for atrial fibrillation detection (ECG or PPG).

Output

The node outputs an array of JSON objects representing the body weight measurements retrieved from the Cardiacsense API. Each object corresponds to a data point within the specified time range and includes:

  • Measurement values such as body weight.
  • Timestamps indicating when the measurement was taken.
  • Optional metadata depending on the Ignore Metadata option (FHIR metadata may be included or omitted).

If the Ignore Metadata option is enabled, the output will be a simplified JSON structure focusing on core measurement data without additional FHIR metadata fields.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Cardiacsense FHIR API.
  • The node expects proper configuration of the API base URL and authorization token via credentials.
  • No other external dependencies are required.

Troubleshooting

  • Common Issues:

    • Invalid or missing patient email can cause the API to return errors or empty results.
    • Incorrect date/time formats for start or end times may lead to request failures.
    • Using unsupported device types or invalid averaging intervals might result in unexpected responses.
    • Network or authentication issues with the Cardiacsense API will cause HTTP request failures.

  • Error Messages:

    • "Unknown operation: getBodyWeight": Indicates the operation name is incorrect or not supported; verify spelling and case.
    • "Unknown patient management operation": Occurs if the resource or operation parameters do not match expected values.
    • HTTP 401 Unauthorized: Check that the API key credential is valid and properly configured.
    • HTTP 400 Bad Request: Usually due to malformed parameters like invalid dates or missing required fields.

To resolve these errors, ensure all required properties are correctly set, credentials are valid, and input formats conform to expectations.

Links and References

Discussion