Skip to main content

Patient intake agent

Complete answers are not clinical conclusions.

A patient intake agent helps people complete approved forms, review their answers and send the relevant information to the right healthcare team. It can explain questions and prepare source-linked summaries without changing patient-reported meaning. Werkon would validate this intake workflow with accessible human assistance; qualified staff retain clinical assessment, consent review and decisions about authoritative records.

Use the right form and preserve each answer

Registration, history, medication, allergy, symptom, referral, insurance, consent and records-request forms need different fields and owners. Select the approved version for the purpose and audience. Identify the patient, respondent, representative and recording source separately; a household relationship does not establish proxy authority.

Explain required and optional fields, sensitive-data purpose and conditional questions. Keep unanswered, declined, unknown, not applicable and not asked distinct. Prefilled values need a source and date, with confirmation where current accuracy matters. Preserve original words and attachments alongside any normalized candidate.

Make completion accessible and correctable

Allow save, resume, review, correction and stopping without losing provenance. Support keyboard, screen readers, zoom, reflow, mobile, low-bandwidth and staff-assisted use. Avoid unnecessary time limits or repeated entry; identify errors in text and move focus predictably.

Deterministic checks validate formats, units, ranges, required fields and branching, without declaring an answer clinically true. Inspect uploaded documents before authorized viewing. Consent remains a separate purpose-, actor-, data-, action- and period-specific workflow with verification and revocation.

Follow submission through qualified review

Patient confirmation and a durable submission receipt do not establish staff review, triage, an appointment or care. Route only the approved subset to named teams and record delivery and acceptance independently. Qualified staff assess identity, proxy authority, medication conflicts, safeguarding and clinical content.

Use fixed urgent-contact or emergency instructions from approved clinical policy when required, and describe monitoring hours honestly. Authoritative clinical fields require approved review and retained patient-reported provenance; no silent medication or allergy overwrite is permitted. Amendments and corrections remain linked to the submitted form version.

Intake boundary

Collect the account without claiming the conclusion.

A form can establish that a required answer was supplied. Four boundaries keep that mechanical completion separate from identity, clinical meaning and operational follow-through.

01

Subject, respondent, authority, and purpose

Resolve the patient or prospective patient, authenticated user, subject, answer source, recorder and representative relationship; bind the request, service, encounter and purpose; and ask only the approved minimum information.

Required evidence: Organization and tenant, patient candidate and match evidence, authenticated session, subject, source and author roles, representative documentation, request or referral, service and encounter context, purpose, privacy notice, access scope, correction and exception history.

02

Approved form, language, and accessible presentation

Select the exact questionnaire version and effective period, preserve order and conditional logic, label inputs and errors, distinguish required from optional and support language, disability, device, save, resume, stop and staff-assisted alternatives.

Required evidence: Questionnaire canonical identifier and version, owner and status, effective period, jurisdiction and audience, item and link identifiers, instructions, data type, required and repeating state, enable conditions, language version, accessibility checks, session progress and support request.

03

Patient-provided answers and validation

Preserve original words, uploads, prefill sources and missing reasons; validate exact structure and completeness; show errors and corrections; and keep normalization, screening calculations and AI candidates distinct from the submitted response.

Required evidence: Response and item identifiers, in-progress or completed state, answer value and unit, original text, source and authored time, prefill source and confirmation, missing reason, validation result, attachment digest and scan, calculation inputs, normalized candidate, correction and submission digest.

04

Consent, staff handoff, and record reconciliation

Handle consent as a separate scoped choice, route approved answer subsets to named teams, distinguish delivery from review, require qualified clinical interpretation and preserve patient confirmation, staff disposition, field-level incorporation and later correction.

Required evidence: Consent policy, decision, provisions, purpose, actor, data, period, verification and revocation; routing rule and payload; queue, acknowledgment, acceptance and reviewer; urgent escalation; disposition and rationale; authoritative field mapping; patient receipt; amendment, entered-in-error and outcome reconciliation.

Question-to-disposition path

Keep each answer attached to who said it and why it was asked.

Intake information changes meaning when subject, source, purpose or time is lost. Each stage preserves those dimensions through staff use.

  1. 01

    Resolve the intake context

    Identify the organization, patient candidate, authenticated respondent, subject, representative relationship, request and service; explain purpose and privacy; minimize fields; and hold ambiguous identity or authority for staff support.

    Owner
    Patient-access, identity, privacy and records owners
    Evidence
    Patient candidate and match result, respondent and source, representative evidence, request and service context, purpose, notice, approved field set, access decision, ambiguity, staff handoff and correction path.
  2. 02

    Present the approved accessible form

    Load the current form and language, apply deterministic branching, show instructions and required state, preserve optional and declined paths and support keyboard, assistive technology, zoom, mobile, low bandwidth, save, resume and human assistance.

    Owner
    Form, clinical-content, language-access, accessibility and technology owners
    Evidence
    Questionnaire identifier and version, effective date, item order, labels and instructions, enablement trace, required status, language, accessibility test, session state, timeout behavior, support request and fallback completion path.
  3. 03

    Validate without interpreting

    Preserve answers and missing reasons, scan attachments, apply data-type, format, range, unit, required and conditional checks, identify errors in text and let the respondent review and correct without silently changing the response.

    Owner
    Intake-platform, security, clinical-content and data owners
    Evidence
    Response state and version, answer and source, prefill confirmation, attachment type and scan, exact validation rule and result, text error and suggestion, respondent correction, calculation inputs, unanswered reason and completed-response digest.
  4. 04

    Confirm, consent, and route

    Show the complete response and sensitive disclosures for confirmation, run any separate consent flow, issue a receipt and route only authorized subsets through deterministic rules while urgent or ambiguous cases reach named staff promptly.

    Owner
    Patient, privacy, consent, patient-access and clinical-operations owners
    Evidence
    Review display, patient confirmation, submitted version, consent decision and scope, receipt, route and payload, queue event, acknowledgment, urgency rule, escalation attempt, staff acceptance, due time and failure recovery.
  5. 05

    Review, incorporate, and reconcile

    Require qualified interpretation, preserve staff disposition and patient-reported provenance, apply approved field-level changes, notify the patient of required next steps and reconcile amendments, record corrections, access failures and service outcomes.

    Owner
    Clinical, records, patient-access, authorization, billing and quality owners
    Evidence
    Reviewer and evidence viewed, clinical or administrative disposition, field mapping and prior value, source label, next-step message, appointment or referral state, amended or entered-in-error response, patient correction, complaint, missed escalation and outcome variance.

Authority map

Separate form logic, language assistance, and qualified interpretation.

Software can tell that a field is empty. It cannot decide what a symptom means, whether consent is valid or what care a person needs.

01

Deterministic intake controls

Software owns tenant boundaries, session identity, questionnaire versions, item order, branching, required fields, types, formats, ranges, units, scoring arithmetic, attachment controls, consent enforcement hooks, routing, version state, access and receipts.

  • Patient, subject, respondent, questionnaire, response and request identifiers
  • Required, optional, conditional, repeated, missing and correction state
  • Data-type, format, range, unit, attachment, completeness and route checks
  • Save, resume, submit, consent, delivery, acknowledgment and amendment receipts
02

Bounded AI assistance

Models can explain approved questions, extract fields from patient-provided documents, map free text to source-linked candidates, identify possible missingness or contradiction and draft summaries while preserving the original answer.

  • Plain-language explanation and approved-language draft candidates
  • Document and free-text extraction candidates with citations
  • Duplicate, contradiction and incomplete-answer candidates
  • Staff handoff and patient next-step message drafts
03

Human patient and professional authority

Patients or authorized representatives own their answers and corrections; qualified staff own identity and proxy resolution, clinical interpretation, urgency, capacity, consent validity, service routing, record incorporation, care and complaints.

  • Patient answer, confirmation, decline and correction authority
  • Identity, representative, capacity and consent decisions
  • Clinical interpretation, urgency, safeguarding and care decisions
  • Record, referral, appointment, billing, complaint and redress decisions

Intake components

Build an answer lineage, not a registration blob.

The same value can come from the patient, a representative, an old record or automated extraction. Four components preserve that difference.

01

Identity, purpose, and access registry

Bind organization, patient candidate, authenticated user, subject, answer source, recorder, representative relationship, request, service, encounter, purpose, privacy notice, access, language and correction paths.

Operating contract: Authenticated user is not automatically the patient, representative relationship is not authority for every purpose, subject is not always respondent, household access must not cross records and a request for service is not an appointment or clinical acceptance.

02

Questionnaire and presentation registry

Version owner-approved forms, effective periods, audiences, languages, instructions, item order, link identifiers, data types, options, required and repeating state, enable conditions, scores, accessibility evidence and retirement.

Operating contract: Published form is not clinically appropriate for every person, required is purpose-specific, hidden questions must not retain stale answers, a calculated score is not diagnosis or triage and technical conformance is not universal accessibility.

03

Response and consent ledger

Preserve in-progress, completed, amended, entered-in-error and stopped responses; original and normalized answers; source, author and subject; missing reasons; attachments; errors; confirmations; and separate consent decision, provisions, verification and revocation.

Operating contract: Completed is not clinically true, blank is not no, prefilled is not confirmed, source is not always subject, attachment is untrusted, consent record is not legal sufficiency and consent representation must be enforced by current access policy outside the model.

04

Handoff and record-outcome ledger

Link approved routing payloads, queue and acknowledgment, staff acceptance, urgent escalation, review, disposition, field-level incorporation, patient receipt, next steps, amendment, correction, complaint and service outcome.

Operating contract: Submitted is not delivered, delivered is not accepted, accepted is not reviewed, review is not triage or care, copied value must retain patient-reported provenance and later correction must not erase what the respondent originally submitted.

Delivery path

Prove one intake form through staff disposition.

Start with one form and service path whose respondents, accessibility needs, current staff work and downstream record changes can be observed.

  1. 01

    Choose one bounded intake path

    Select one form, service and respondent cohort with an approved purpose, known identity and representative rules, current content owner, named review team, accessible alternative and observable downstream disposition.

  2. 02

    Map questions, sources, and decisions

    Inventory every field, why it is needed, who can answer, prefill sources, branching, missing states, consent, urgent instructions, attachments, routing, review, record targets, correction and current burden.

  3. 03

    Build accessible validation and lineage

    Implement labels, instructions, errors, keyboard and assistive-technology flows, save and resume, exact answer provenance, deterministic form checks, secure attachments, patient confirmation, receipts and controlled routing.

  4. 04

    Test difficult intake cases

    Exercise wrong patient, representative limits, shared device, language and literacy needs, screen reader and zoom, poor connection, interrupted session, conditional questions, blank versus no, sensitive decline, conflicting prefill, unsafe attachment and urgent content.

  5. 05

    Release narrowly and reconcile staff use

    Begin with one staffed queue, compare completion and correction with the current path, monitor exclusion and false urgency and follow each submission through acceptance, review, field incorporation, patient correction and service outcome.

Release controls

Six controls before answers can enter an authorized workflow.

Intake can expose sensitive information or delay care when its boundaries fail. These controls keep collection minimal, usable and accountable.

Subject, respondent, and purpose remain explicit
Resolve patient and request context, distinguish subject, source and recorder, establish representative scope, explain why information is collected, enforce tenant access and hold ambiguous identities rather than merging records.
Forms are approved, current, and accessible
Version clinical and administrative ownership, effective dates, language and branching; label every input; identify errors in text; support correction, save, resume and assistive technology; and retain staff-assisted alternatives.
Missingness and patient words survive
Keep blank, declined, unknown, not applicable and not asked distinct; preserve original language and attachments; cite prefill and normalization; require confirmation where material; and prevent silent coercion or auto-correction.
Validation never becomes clinical interpretation
Check structure, type, format, range, unit and completeness deterministically; label scores and model candidates; use fixed approved urgent instructions; and route symptoms, medications, allergies, capacity and safeguarding questions to qualified staff.
Consent and access are separately enforced
Present purpose-specific choices without preselection, preserve permit, deny, exceptions, period, verification and revocation, confirm applicable legal requirements and enforce data access through deterministic current policy outside the model.
Delivery, review, and correction are observable
Record submission, delivery, acknowledgment, staff acceptance, review, escalation and field-level use separately; issue a patient receipt; retain provenance; and propagate amendments and entered-in-error decisions to every affected record and owner.

Outcome evidence

Measure usable handoffs and corrected records, not submissions.

A higher completion count can hide abandonment, inaccessible paths and unresolved clinical information. Evidence must follow what people could provide and what staff did with it.

Baseline

  • Forms, purposes, services, respondent and representative patterns, languages, disabilities, devices, connection conditions, sensitive fields, staff queues, record targets and correction paths
  • Current time and human effort from identity and explanation through completion, support, correction, staff review, field entry, appointment or referral and complaint resolution
  • Current abandonment, repeated entry, input errors, missing reasons, stale prefill, duplicate records, inaccessible tasks, unsafe attachments, urgent responses and unacknowledged submissions
  • Current staff corrections, clinical escalations, consent disputes, record amendments, appointment or service outcomes, complaints, privacy incidents and missed follow-up

Outcome evidence

  • Correct patient, subject, respondent, source, representative, request, purpose, questionnaire, version, language and route handling against approved evidence
  • Completion, error recovery, support use, abandonment, correction and staff effort by language, disability, device, connection, form branch and respondent type
  • Cross-record, over-collection, inaccessible-control, blank-to-false, stale-prefill, unsafe-attachment, coerced-consent, lost-submission and unowned-urgent-case prevention
  • Staff disposition, authoritative-field correction, appointment or referral progress, patient correction and complaint outcome against the submitted response with operational confounders visible

Guardrails

  • Wrong patient or tenant, unsupported representative, shared-session disclosure, excessive fields, hidden purpose, inaccessible authentication, silent timeout and no viable staff-assisted path
  • Unlabeled input, error shown only by color, branch losing answers, blank called no, patient wording overwritten, stale prefill called current, optional disclosure forced and attachment executed or exposed
  • Completion called clinical accuracy, score called diagnosis or triage, model-selected urgency, consent preselected, permit generalized, urgent content left in an unmonitored queue and qualified review bypassed
  • Submitted called received, received called reviewed, review called care, record provenance lost, amendment not propagated, correction discouraged and intake activity presented as access, health or compliance outcome

Fit test

Use this pattern when one form can be followed through staff action.

Good reason to begin

  • One intake form has a defined purpose, current content owner, known respondent and representative rules, accessible alternatives, named staff queue and downstream record or service evidence.
  • Questionnaire version, patient-provided response, prefill, normalization, consent, routing, staff review and authoritative record can remain linked but distinct.
  • The organization can preserve missingness, patient language, correction, screen-reader and mobile behavior, save and resume, manual support and urgent escalation without overstating clinical meaning.
  • Identity mismatch, inaccessible flow, sensitive decline, unsafe attachment, interrupted submission, queue failure, urgent content and patient correction can be tested safely.

Resolve before beginning

  • Purpose, form ownership, representative authority, language, accessibility, urgent-content policy, consent, staff review, record mapping or correction ownership is undefined.
  • The process cannot preserve subject, source and author or distinguish response, validation, consent, delivery, clinical review, record incorporation and service outcome.
  • Success is defined by completed forms without abandonment, error recovery, accessibility segments, staff burden, correction, urgent escalation and downstream outcome evidence.
  • The agent is expected to infer identity or consent, diagnose, triage, recommend care, update clinical lists, confirm insurance, book services or replace qualified staff autonomously.

Source basis

Sources behind the control model.

  • 01

    Health Level Seven International

    HL7 FHIR Release 5 Questionnaire resource

    The current published FHIR R5 version 5.0.0 trial-use Questionnaire resource defines an ordered and grouped set of questions, instructions, answer constraints, required and repeating items and conditional enablement. It does not establish that a form is clinically appropriate, minimal, current, understandable, accessible, legally sufficient or safe for a particular person and purpose.

  • 02

    Health Level Seven International

    HL7 FHIR Release 5 QuestionnaireResponse resource

    The current published FHIR R5 trial-use response distinguishes subject, source and author and supports in-progress, completed, amended, entered-in-error and stopped states. Completion means the associated questionnaire requirements are met, not that identity, answer accuracy, clinical interpretation, urgency, consent, staff review, record incorporation or care has been established.

  • 03

    Health Level Seven International

    HL7 FHIR Release 5 Consent resource

    The current published FHIR R5 trial-use Consent resource can represent a healthcare consumer's or third party's permit or deny choice, verification and exceptions by actor, data, purpose and period. HL7 states that enforcement is outside the resource. A structured consent does not prove identity, capacity, authority, informed choice, legal validity, current applicability or actual access enforcement.

  • 04

    World Wide Web Consortium

    Web Content Accessibility Guidelines 2.2

    The current W3C Recommendation includes input-assistance criteria for text error identification, labels or instructions, correction suggestions and error prevention, alongside keyboard, focus, reflow and accessible-authentication requirements. Conformance is a testable accessibility baseline, not proof that one form is understandable, equitable, clinically suitable or accessible to every individual and assistive setup.

[ WORKFLOW / SYSTEMS AUDIT ]
THE FIRST ENGAGEMENT

Start with one real workflow

A Systems Audit is the usual starting point. If the opportunity is already clear, we can move directly into a focused build.

Show Us the WorkflowStart with the free automation readiness checklist

OBSERVEQUANTIFYDECIDEBUILD

Continue with the work

Choose the next useful path.

Stay with the operating question. The technology can wait until the work is clear.

01

Health insurance verification assistant

Connect patient intake to coverage evidence and unresolved questions without promising eligibility.

Open path02

Explore governed AI agents

Compare other bounded agent patterns and the evidence, authority and recovery contracts they require.

Open path03

Design healthcare administration

Frame patient access, intake, billing and communication around protected information, qualified authority and observed practice outcomes.

Open path04

Coordinate appointment access

Keep patient, service, resource, eligibility, booking, communication and attendance states distinct through scheduling.

Open path05

Build an accessible custom application

Turn forms, permissions, validation, queues and records into a secure, testable and maintainable application workflow.

Open path