Consultorio Live icon

Consultorio Live

Interagir com a API do Consultorio Live para gestão de clínicas e consultórios

Actions20

Overview

This node integrates with the Consultorio Live API to manage clinical and medical office data. Specifically, the "Prontuário" (Medical Record) resource with the "Criar" (Create) operation allows users to create new medical records in the system. This is useful for healthcare providers who want to digitally document patient encounters, diagnoses, medications, and related appointment information.

Typical use cases include:

  • Automatically creating a medical record after a patient visit.
  • Storing detailed notes, diagnoses, and prescribed medications linked to patients and professionals.
  • Integrating with scheduling systems by associating records with appointment IDs.

Properties

Name Meaning
Dados Do Prontuário A collection of fields describing the medical record details:
- Conteúdo The content or notes of the medical record (required).
- Data The date and time of the medical record entry (required).
- Diagnósticos Comma-separated list of diagnoses related to the record.
- ID Do Agendamento Identifier of the related appointment (optional).
- ID Do Paciente Identifier of the patient associated with the record (required).
- ID Do Profissional Identifier of the professional who created the record (required).
- Medicações A collection of medications prescribed, each including:
-- Nome Medication name (required).
-- Dosagem Dosage information (optional).
-- Frequência Frequency of medication usage (optional).

Output

The node outputs JSON data representing the newly created medical record as returned by the Consultorio Live API. This typically includes identifiers, timestamps, and all submitted fields confirming successful creation.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the Consultorio Live API.
  • The base URL for the API must be configured in the node credentials.
  • The node sends requests with Accept: application/json and Content-Type: application/json headers.

Troubleshooting

  • Missing Required Fields: Errors may occur if required fields like patient ID, professional ID, content, or date are missing. Ensure all mandatory inputs are provided.
  • Authentication Failures: If the API key or base URL is incorrect or missing, authentication errors will arise. Verify credential configuration.
  • Invalid Date Format: The date field must be a valid datetime string; otherwise, the API may reject the request.
  • API Limitations: The API might enforce limits on field lengths or allowed values (e.g., diagnoses format). Check API documentation if errors mention invalid input.
  • Network Issues: Connectivity problems can cause request failures. Confirm network access to the API endpoint.

Links and References

Discussion