Actions20
Overview
The node "Consultorio Live" integrates with the Consultorio Live API, which is designed for managing clinics and medical offices. Specifically, the "Get Many" operation under the "Prontuário" (Medical Record) resource allows users to retrieve multiple medical records filtered by patient ID. This operation is useful in scenarios where a user needs to fetch all medical records associated with a particular patient, such as when reviewing patient history or preparing reports.
Practical examples include:
- A clinic system fetching all medical records of a patient before an appointment.
- Generating summaries or exporting patient medical histories for administrative purposes.
Properties
| Name | Meaning |
|---|---|
| Parâmetros De Busca | Collection of search parameters to filter medical records. |
| - ID Do Paciente | The patient ID used to filter and retrieve medical records belonging to that patient. |
The "Parâmetros De Busca" property is a fixed collection containing one required field:
- ID Do Paciente: A string representing the unique identifier of the patient whose medical records are to be retrieved.
Output
The node outputs JSON data containing the list of medical records matching the provided patient ID. Each item in the output corresponds to a medical record object as returned by the Consultorio Live API.
If the API supports binary data related to medical records (e.g., attached documents or images), the node would handle it accordingly, but based on the provided code and properties, the primary output is structured JSON data representing medical records.
Dependencies
- Requires connection to the Consultorio Live API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for the API is dynamically set from the credentials configuration.
Troubleshooting
- Missing or invalid patient ID: Since the patient ID is required, omitting it or providing an incorrect value will likely result in errors or empty results. Ensure the patient ID is correctly specified.
- Authentication errors: If the API key or token is missing or invalid, the node will fail to connect. Verify that the API credentials are properly configured.
- API connectivity issues: Network problems or incorrect base URL settings can cause request failures. Confirm the API endpoint and network access.
- Empty results: If no medical records are found for the given patient ID, the output will be empty. Double-check the patient ID and data availability.
Links and References
- Consultorio Live API Documentation (Assumed link; replace with actual if available)
- n8n Documentation on Creating Custom Nodes