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 advanced cardiovascular and monitoring metrics for patients. Specifically, the Get Real-Time Data operation under the Advanced Metrics resource fetches real-time cardiac and health monitoring data within a specified time range for a given patient.

Typical use cases include:

  • Monitoring a patient's heart-related metrics in near real-time for clinical or research purposes.
  • Aggregating cardiovascular data over a custom time interval to analyze trends or detect anomalies.
  • Integrating cardiac device data (e.g., from CardiacSense Watch) into healthcare workflows or dashboards.

For example, a healthcare provider could use this node to pull a patient's heart rate variability and atrial fibrillation detection data between two timestamps to assess cardiac health during a hospital stay.

Properties

Name Meaning
Patient Email Email address of the patient whose data is being retrieved.
Start Time Start date/time for data retrieval in YYYY-MM-DD or YYYY-MM-DD HH:MM:SS format.
End Time End date/time for data retrieval 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 where measurement originated: CardiacSense Watch, External Device, or Manual by User.
- AF Source Source for atrial fibrillation detection: ECG (Default) or PPG. (Shown only for specific operations.)

Output

The node outputs an array of JSON objects representing the requested advanced metric data for the patient within the specified time range. Each object corresponds to a data point or aggregated metric returned by the Cardiacsense API.

  • The output JSON structure depends on the selected operation but generally includes timestamped cardiovascular measurements.
  • If the "Ignore Metadata" option is enabled, the response excludes detailed FHIR metadata, providing a simplified dataset.
  • No binary data output is produced by this node.

Example output snippet (simplified):

[
  {
    "timestamp": "2024-01-01T08:00:00Z",
    "heartRate": 72,
    "atrialFibrillationDetected": false,
    "device": "cardiacsense_watch"
  },
  ...
]

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 these credentials.
  • Network access to the Cardiacsense API endpoints is necessary.
  • No additional external libraries beyond n8n core dependencies are required.

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.
    • Selecting unsupported operations or resources will throw an error.
    • Network connectivity issues or invalid API tokens will cause authentication failures.

  • Error Messages:

    • "Unknown operation: <operation>": Indicates the operation name is not recognized; verify spelling and supported operations.
    • "Unknown patient management operation: <operation>": Occurs if an unsupported patient management operation is selected.
    • HTTP errors from the API (e.g., 401 Unauthorized) suggest invalid credentials or expired tokens.

  • Resolutions:

    • Ensure all required fields are correctly filled with valid values.
    • Confirm API credentials are up to date and have proper permissions.
    • Use ISO-compliant date/time strings for start and end times.
    • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion