Dr. Daniel Karni
All projects

Sheet 01 · Before the visit

Digital Health Declaration

Status: Built Still in testing, not yet in use. As of 30.09.2026.

In plain words

The patient confirms details already on file, answers a short list of health history questions on a phone and signs. A person reviews the flagged answers.

Title block

Status
Status: Built Still in testing, not yet in use.
Engine
Engine: no AI The question set is data; flags are rules.
Human check
A person reviews flagged answers and countersigns separately.
Data touched · Reviewed
Data touched
The patient's own answers and identity details already on file.
Reviewed
30.09.2026 · Rev A

Runs on hardware Dr. Karni controls. As of 30.09.2026. Designed by me. Built with AI coding assistants.

Step 1 The form on a phone
A sample health form on a drawn phone, reached from a link or QR code.Link or QRSample Adetails on fileconfirmQuestion 1 (yes/no)YesNoQuestion 2 (yes/no)YesNoSign here
Step 2 The signed page
The signed page, with one answer flagged and a checksum strip along its foot.Sample ASigned PDFflagSignedchecksum
Step 3 Review and countersign
A review queue; a person countersigns on a separate page.reviewSample AflagSample BSample Ccountersign
Drawn, not captured. Fictional data.
Text version

Step 1: a phone shows Sample A's details already on file and questions, each answered yes or no. Step 2: the signed page, with a checksum strip along its foot and one answer flagged. Step 3: a review queue where a person countersigns on a separate page.

What it does

A link or QR code shown in the clinic opens a health history form on the patient's phone. Details already on file are confirmed rather than retyped, and the patient answers a short list of health history questions.

Follow-up detail opens only where an answer is yes. The patient signs with a finger.

Each submission is filed as a PDF that carries a checksum, and a person reviews flagged answers in a queue and countersigns separately. It is automation, not AI.

How it works

  1. A link or QR code shown in the clinic opens the form on the patient's phone.
  2. Details already on file are confirmed, not retyped.
  3. Yes/no questions; detail opens only after a yes.
  4. The patient signs with a finger, and a PDF with a checksum is filed.
  5. A person reviews flagged answers and countersigns separately.

What it will not do

  • Assess the answers. Flags are rules for a person to review, not a clinical judgement.
  • Change a signed declaration. A countersignature is a separate page.
  • Send anything by itself. A person shares the link.
For colleagues

The question set lives in one data file, so a change to the questions is a new version rather than a code change. The countersignature is a separate addendum; it does not edit the patient's signed page.