Requirements, packets and patient links

Requirements connect templates to the clinical workflow. When an appointment matches, Menaela can prepare the needed instances and group them into one patient packet.

In this pageAttach documents to the visit workflow · Instances freeze the relevant context · One packet instead of several unrelated links · Prepare and send through Main Menaela

Attach documents to the visit workflow

A template can be made a requirement for an initial visit or for a specific service. Requirements can also carry recurrence rules so the clinic can distinguish one-time intake from documents that need to be collected again.

Instances freeze the relevant context

When a requirement becomes a patient document instance, the relevant placeholder data is snapshotted for that instance. Later changes to the clinic or appointment do not silently rewrite what the patient was originally asked to complete.

One packet instead of several unrelated links

  1. Menaela resolves which forms and questionnaires are required for the patient and appointment.
  2. The system creates the necessary document instances.
  3. Those instances are bundled into one packet.
  4. The patient receives one opaque public link valid for 48 hours.
  5. Staff can track status, reissue a new link if needed, or cancel the packet.

Prepare and send through Main Menaela

Authorized staff can ask Menaela to prepare or send the required packet instead of manually assembling links. Menaela can also list existing templates, retrieve patient document status, reissue a packet or cancel one when the workflow requires it.