Document activity

Documents generated, last 14 days

EnglishSpanish

By clinic

last 30 days

Output language

Recent documents

Patient	Clinic	Language	Created

Generation engine

measured in this browser

Server batch test

500 documents in 8.1 s on one Node.js process, about 60 per second. The daily target of 500 is a few seconds of work for one worker.

Active templates

Patient Intake Form

Each field is mapped into the master Word template. One submission produces a branded .docx and a PDF.

01Form

02Mapping

03Render

04DOCX + PDF

00Output settings

Clinic brand profile Brand colour

Document language

English Español

01Patient informationRequired

First name * Last name * Date of birth * Age is calculated from the date of birth Sex * Phone number * Email Street address * City *

State * ZIP *

Preferred language

02Emergency contactRequired

Full name * Relationship * Phone number *

03InsuranceConditional

Insurance provider * Provider name * Member ID * Group number Policy holder Policy holder name *

Self-pay: the insurance block is left out and the document prints a self-pay notice instead.

04Reason for visitRequired

Visit type * Visit date * Symptoms for Reason for visit *0 / 600 Pain level: 0 / 10

05Medical background

Any known allergies? *

No Yes

Allergies and reactions *

Current medications

06Consent and signatureRequired

I confirm the information is accurate and I consent to examination and treatment. * Type full name to sign * Must match the patient name

Documents

Every document is rebuilt from its stored data and the current template when downloaded.

New intake document

Reference	Patient	Clinic	Visit	Coverage	Lang	Created

Templates

Master templates are ordinary Word files. Merge fields, conditional sections and repeating rows below are read directly from each .docx.

Brand profiles

One master template serves every clinic. The brand colour and logo are applied when the document is rendered.

API

The REST interface planned for the MVP. CRM, EHR and ERP systems send the same data the form produces.

Proof of concept note. Here the engine runs in the browser so the demo needs no server. In the MVP the same engine runs behind this endpoint on Azure, with queue-based workers.

Generate a document

POST/api/v1/documents

template	Template key, for example `patient_intake_en`
brand	Brand profile id, or colour and logo overrides
output	`["docx","pdf"]`
data	Field values, the same shape as the form
callback_url	Optional webhook, called when the files are ready

Response

{
  "id": "PI-261012-7QXA",
  "status": "completed",
  "files": {
    "docx": "https://.../PI-261012-7QXA.docx?sig=...",
    "pdf":  "https://.../PI-261012-7QXA.pdf?sig=..."
  },
  "render_ms": 412
}

Example request

built from your latest document

Document activity

Documents generated, last 14 days

By clinic

Recent documents

Generation engine

Patient Intake Form

00Output settings Load sample patient

01Patient informationRequired

02Emergency contactRequired

03InsuranceConditional

04Reason for visitRequired

05Medical background

06Consent and signatureRequired

Documents

Templates

Brand profiles

API

Generate a document

Example request

00Output settings