MedX65 icon

MedX65

Interact with MedX65 medical system API
Join our community

Actions7

Overview

This node integrates with the MedX65 medical system API to manage agenda entries (appointments or scheduled events). Specifically, the "Agenda - Create" operation allows users to create new agenda entries by specifying details such as user ID, start and end times, description, status, and optionally linking the entry to a patient.

Common scenarios where this node is beneficial include:

  • Scheduling appointments for medical staff or users within a healthcare system.
  • Creating calendar entries linked to patients for tracking consultations or procedures.
  • Automating agenda management in medical workflows by programmatically adding new events.

Practical example:

  • A clinic's automation workflow creates an agenda entry when a new patient consultation is booked, specifying the responsible user, appointment time, description, and linking it to the patient record.

Properties

Name Meaning
User ID The ID of the user responsible for the agenda entry (e.g., doctor or staff member).
Start Date The starting date and time of the agenda entry.
End Date The ending date and time of the agenda entry.
Description Text description of the agenda entry (e.g., reason for appointment).
Status Numeric status ID for the agenda entry, typically 1 for active or default status.
Linked To (Patient ID) Optional patient ID to link this agenda entry to a specific patient record.

Output

The node outputs JSON data representing the response from the MedX65 API after creating the agenda entry. This typically includes confirmation details of the created agenda item or error information if creation failed.

The output structure is an array of objects, each containing a json field with the API response. For example:

[
  {
    "json": {
      "Id_do_Usuario": 123,
      "Inicio": "2024-06-01T09:00:00Z",
      "Final": "2024-06-01T10:00:00Z",
      "Descricao": "Consultation",
      "Status": 1,
      "Vinculado_a": 456,
      "Result": "Success",
      "AgendaId": 789
    }
  }
]

No binary data output is produced by this operation.

Dependencies

  • Requires an API authentication token credential for the MedX65 system.
  • The node makes HTTP requests to the MedX65 API endpoint at https://medx65-v65teste.azurewebsites.net.
  • The integration token is used to obtain an authorized bearer token before making API calls.
  • Proper configuration of the API credentials in n8n is necessary for successful operation.

Troubleshooting

  • Common issues:

    • Invalid or expired API token causing authorization failures.
    • Missing required fields such as user ID, start/end dates, or description.
    • Incorrect date formats leading to API validation errors.
    • Network connectivity problems preventing access to the MedX65 API.

  • Error messages and resolutions:

    • Authorization errors: Ensure the API key credential is valid and has not expired.
    • Validation errors from the API: Verify all required properties are provided and correctly formatted.
    • Request failures: Check network connection and API endpoint availability.
    • If the node throws an error but "Continue On Fail" is enabled, the error message will be included in the output JSON under an error property.

Links and References

Discussion