CardiacsenseInstall

Overview

This node integrates with the Cardiacsense FHIR API to manage patient-related data, specifically supporting operations under the "Patient Management" resource. The "List Patients" operation retrieves detailed patient information filtered by parameters such as patient email and time range.

Common scenarios for this node include:

• Fetching a list of patients associated with a particular email address within a specified date/time range.
• Retrieving patient data for further processing or analysis in healthcare workflows.
• Integrating patient monitoring data into broader health management systems.

Practical example:

• A healthcare provider wants to pull all cardiac monitoring data for a patient identified by their email between January 1st and January 2nd, 2024, to review recent heart rate trends.

Properties

Output

The node outputs an array of JSON objects representing patient data retrieved from the Cardiacsense API. Each item corresponds to a patient record or related data depending on the operation.

• The output JSON structure directly reflects the API response, including patient details and associated metadata unless the "Ignore Metadata" option is enabled.
• No binary data output is indicated for this operation.

Example output snippet (simplified):

[
  {
    "patient_email": "patient@example.com",
    "name": "John Doe",
    "age": 45,
    "measurements": [
      {
        "timestamp": "2024-01-01T08:00:00Z",
        "heart_rate": 72,
        "device": "cardiacsense_watch"
      }
    ]
  }
]

Dependencies

• Requires an API key credential for authenticating with the Cardiacsense FHIR API.
• The node uses HTTP GET requests to endpoints under the base URL provided by the credential.
• Proper configuration of the API token and base URLs in n8n credentials is necessary.

Troubleshooting

• Common issues:

  • Invalid or missing API authentication token will cause authorization errors.
  • Incorrect date/time formats for start or end times may result in request failures.
  • Providing an unknown operation name will throw an error indicating the operation is unsupported.
  • Missing required parameters like patient email will cause validation errors.

• Error messages:

  • "Unknown patient management operation: <operation>": Check that the operation name is correctly set to "listPatients".
  • Authorization errors: Verify that the API key credential is valid and has proper permissions.
  • Request failures due to invalid query parameters: Ensure date/time strings follow the expected format.

• To resolve errors, verify input parameters, ensure credentials are configured correctly, and consult API documentation for valid values.

Links and References

• Cardiacsense API Documentation (hypothetical link for reference)
• FHIR Standard Overview
• n8n Documentation on Creating Custom Nodes