Larch & LinnetHealth
Sample dataPrototype with sample data. Nothing is saved to a server and nothing is sent.

Registration home / How it works

How the system fits together.

Registration, referral, QR check-in and a staff workspace in one custom-built system. Nothing here is a template.

The flow

  1. Register or refer

    An eight-step form on any device, with a tap-on body map and questions that appear only when they apply. Doctors’ offices use a short referral form instead.

  2. Scan to start

    A sign in the waiting room carries a QR code that opens the registration. Another carries the check-in code.

  3. Check in

    Scan the door sign on a phone, or show the code on the confirmation to the front desk. The waiting-room board updates.

  4. Care and follow-up

    Clinicians see review prompts, send a short progress questionnaire and watch the trend. The front desk keeps the waitlist, recalls and claims moving.

Try the registrationOpen the front desk

What is real here, and what is not

This is a prototype for discussion. It has no server and collects nothing. The right-hand box in each row is what a live version would need.

  • Patient data

    In this sampleInvented people only. Everything stays in this browser tab (memory, with a sample draft in session storage). Nothing is sent over the network.
    In a live systemEncrypted in transit and at rest, stored in Canada, collected only as needed, with retention set by the clinic.
  • Sign-in

    In this sampleNone. Anyone can open these pages.
    In a live systemPatients use a single-use link plus a reference and date of birth. Staff use named accounts with a second sign-in step.
  • Who sees what

    In this sampleA switch between Clinician, Front desk and Manager shows the idea on screen.
    In a live systemServer-enforced roles, so each person sees only what the job needs. Every view and export is logged.
  • QR codes

    In this sampleReal, scannable codes made in the page itself. A phone camera can read the signs. The desk scan is simulated: paste a code or click a ticket.
    In a live systemA scanner or tablet camera at the desk, tied to the real schedule, with codes that are single-visit and expire.
  • Check-in board

    In this sampleUpdates when a check-in happens in this same tab, for example from the phone panel on the front desk page.
    In a live systemUpdates for every screen in the clinic at once, from the server, with the schedule from your booking system.
  • Signature and consents

    In this sampleA typed name and three short sample policies.
    In a live systemThe clinic’s own consent forms, versioned, with a record of who accepted which version and when. Whether a typed name is enough is the clinic’s decision with its lawyer.
  • Review prompts

    In this samplePlain rules over the patient’s own answers, for a clinician to look at.
    In a live systemThe same, with rules your clinicians agree. They stay prompts for a person to review. They are never advice or a diagnosis.
  • Messages

    In this sampleDrafted as templates. Nothing is sent.
    In a live systemSent through a service the clinic has approved, with no health details in any message and an easy way to stop.
  • Claims

    In this sampleA tracker with generic statuses: submitted, waiting, approved, needs information.
    In a live systemConnected to the clinic’s billing process. What each payer requires is the clinic’s to set.
  • Export

    In this sampleBrowser print to save a PDF, and a CSV of names, statuses and counts with no health answers.
    In a live systemPermission-gated, logged, and sent to the clinic’s other systems instead of emailed around.

Health-privacy law applies to a live system. It would be reviewed by the clinic’s privacy officer and a lawyer before real use. Nothing on these pages is legal or clinical advice, and the clinic, its people and its policies are invented.