Gravity icon

Gravity

Gravity
Join our community

Actions4

Overview

This node integrates with the Gravity API to perform operations related to healthcare data management. Specifically, the "Patient Read" operation allows users to retrieve detailed information about a patient by their unique identifier within a specified tenant environment.

Common scenarios for this node include:

  • Fetching patient details for display or further processing in healthcare workflows.
  • Integrating patient data retrieval into automated pipelines for clinical or administrative tasks.
  • Synchronizing patient records from Gravity API into other systems.

For example, a user might input a tenant identifier and a patient ID to obtain the patient's demographic and medical record summary, which can then be used downstream in an n8n workflow.

Properties

Name Meaning
Tenant The identifier of the tenant (organization or client) under which the patient is stored.
Id The unique identifier of the patient whose information is to be retrieved.

Output

The node outputs a JSON object containing the full response data returned by the Gravity API for the requested patient. This typically includes all available patient details such as demographics, contact information, medical history, and other relevant attributes as provided by the API.

If an error occurs during the API request, the output will contain an error field with details about the failure.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating requests to the Gravity API.
  • Uses AWS Signature Version 4 signing for request authentication.
  • The base URL for the API is https://api.dev.jit.care.
  • Requires proper configuration of credentials including access key, secret key, and optionally a session token.
  • Depends on the axios HTTP client and aws4-axios for signed requests.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect tenant or patient ID values may result in "not found" errors.
    • Network connectivity problems can prevent successful API calls.
    • Unsupported HTTP methods are guarded against but misconfiguration could lead to errors.

  • Error messages:

    • Errors returned from the API are passed through in the output's error field.
    • If the node throws an "Unsupported HTTP method" error, it indicates a misconfiguration in the operation setup.
    • Authentication errors usually indicate invalid or expired credentials; verify and update them accordingly.

Links and References

Discussion