Cardiacsense icon

Cardiacsense

Interact with Cardiacsense FHIR API for cardiac and health monitoring data
Join our community

Actions26

Overview

The node "Cardiacsense" integrates with the Cardiacsense FHIR API to retrieve advanced cardiovascular and health monitoring data. Specifically, for the Advanced Metrics resource and Get Perfusion Index operation, it fetches perfusion index measurements of a patient within a specified time range.

This node is useful in healthcare scenarios where continuous or periodic cardiac monitoring data is needed for analysis, diagnosis, or tracking patient health remotely. For example, clinicians can use it to obtain perfusion index trends from wearable devices or external monitors to assess peripheral blood flow and vascular health over time.

Practical examples:

  • Retrieving perfusion index data for a patient between two dates to analyze changes during treatment.
  • Aggregating perfusion index values averaged over configurable intervals to smooth out short-term fluctuations.
  • Filtering data by device type (e.g., CardiacSense Watch vs. external device) to compare measurement sources.

Properties

Name Meaning
Patient Email Email address of the patient whose perfusion index 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 perfusion index values.
- Ignore Metadata Boolean flag to return simplified response without FHIR metadata.
- Device Device type for measurement origin; options: CardiacSense Watch, External Device, Manual by User.
- AF Source (Not applicable for this operation; relevant only for atrial fibrillation detection operations.)

Output

The output JSON contains the perfusion index data retrieved from the Cardiacsense API for the specified patient and time range. The structure corresponds to the API's response, typically including:

  • Timestamped perfusion index measurements.
  • Possibly aggregated values if averaging interval is set.
  • Metadata fields unless ignored via the option.

If the "Ignore Metadata" option is enabled, the output excludes FHIR metadata, providing a simplified dataset focused on core measurement values.

No binary data output is produced by this operation.

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 in the credentials.
  • Network access to the Cardiacsense API endpoints is necessary.

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 be rejected by the API.
    • Using unsupported device types or malformed additional options could lead to unexpected results.

  • Error messages:

    • "Unknown operation": Indicates the selected operation is not recognized; verify the operation name.
    • "Unknown patient management operation": Occurs if a patient management operation other than supported ones is chosen.
    • HTTP errors related to authentication usually mean the API key/token is invalid or expired.

  • Resolutions:

    • Ensure all required properties are correctly filled.
    • Validate date/time inputs conform to expected formats.
    • Confirm API credentials are valid and have necessary permissions.
    • Use the "Ignore Metadata" option if FHIR metadata complicates downstream processing.

Links and References

Discussion