CardiacsenseInstall

Overview

This node integrates with the Cardiacsense FHIR API to retrieve cardiac and health monitoring data. Specifically, for the Cardiac Conditions resource and the Get High Pulse Rate operation, it fetches episodes or measurements where a patient's pulse rate is elevated within a specified time range.

Typical use cases include:

• Monitoring patients remotely for episodes of high pulse rate.
• Integrating cardiac alerts into healthcare workflows.
• Analyzing patient heart rate trends over time for clinical decision support.

For example, a healthcare provider could use this node to automatically pull all high pulse rate events recorded by a wearable device for a patient between two dates, enabling timely intervention.

Properties

Output

The node outputs an array of JSON objects representing the high pulse rate data retrieved from the Cardiacsense API. Each object corresponds to a data point or event matching the query criteria.

• The output JSON includes detailed cardiac condition data, potentially including timestamps, pulse rate values, and associated metadata unless the "Ignore Metadata" option is enabled.
• No binary data output is indicated for this operation.

Example output snippet (simplified):

[
  {
    "timestamp": "2024-01-01T08:15:00Z",
    "pulseRate": 120,
    "device": "cardiacsense_watch",
    "metadata": { ... }
  },
  ...
]

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.
• 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.
  • If the API token is expired or invalid, authentication errors will occur.
  • Selecting unsupported devices or options not applicable to the operation might cause unexpected results.

• Error messages:

  • "Unknown operation: getHighPulseRate": Indicates the operation name is not recognized; verify spelling and case.
  • "Unknown patient management operation": Occurs if the resource-operation combination is incorrect.
  • HTTP errors such as 401 Unauthorized or 403 Forbidden suggest credential issues.

• Resolutions:

  • Ensure all required fields are correctly filled.
  • Validate date/time inputs conform to expected formats.
  • Refresh or reconfigure API credentials if authentication fails.
  • Use the "Ignore Metadata" option to simplify output if parsing complex FHIR metadata is problematic.

Links and References

• Cardiacsense Developer API Documentation
• FHIR Standard Overview
• n8n Documentation on Creating Custom Nodes