forMaDforMaD Health Inc.

• Physician Approved
  • Delegates can help prepare drafts; the physician reviews and approves final content
• Works alongside the EMR
  • No direct EMR integration required for the initial workflow

The Problem

Specialty care runs on forms. Prior authorizations, drug access requests, referral letters and funding applications all ask a physician to restate what is already in the chart. The work is repetitive, it takes time away from patients, and it is hardest where treatment is complex and expensive. Tools built into the EMR often only cover generic notes, not the specific forms these specialties depend on.

What forMaD Does

forMaD is trained for one job: mapping what is in a clinical note onto the fields of a specific form or letter. The physician stays in control and reviews every draft before it is used. The workflow is simple: 1) pick the form or letter, 2) paste the relevant clinical information, 3) review and edit the draft, 4) download the completed PDF or use the generated content for a web-based form.

1. Clinical Information to draft
   • Provide the relevant clinical note or source information and generate a structured draft aligned to the selected workflow.
2. Physician + delegate workflow
   • Designed for the way forms are actually completed: physicians provide clinical judgement while administrative staff can support preparation and completion.
3. Multiple workflow types
   • Supports mapped PDFs, common forms with drug-or condition- specific logic, and content generation for web-based or personalized forms.
4. Review before use
   • Generated content is a draft. Users review, edit and approve the information before a document is finalized or transferred to external system.
5. Privacy-conscious design
   • The launch architecture is being hardened around de-identification, controlled data handling. Canadian production hosting and clear retention practices.
6. No direct EMR integration required
   • The initial product can work outside the EMR using clinician-provided source information, while future integrations remain possible where they add value.

• Form billing: Physicians can charge for forms they complete, including Stripe payment links for patients and invoices for other payors such as insurers.

Who It Supports

• Specialist Physicians
  • Less time restarting the chart on forms and letters, while keeping the physician responsible for reviewing and approving final content.
• Administrative & Drug Access Teams
  • Delegates and administrative staff can help prepare drafts and manage workflow while the physician retains final approval.
• Future Sponsored Deployment
  • Pharma – or program – sponsored deployment may ne the explored later, after the physician launch model is established.

Validation & Launch Status

forMaD has been tested with physicians and administrative staff and is preparing for a paid launch in early 2027. Before launch, the focus is Canadian hosting, privacy/security hardening, physician-and-delegate workflows, and production readiness.

• Now
  • Core note-to-form drafting
  • Physician and delegate workflow refinement
  • Production and privacy/security preparation
• Next
  • Paid launch in early 2027
  • Founding-physician access
  • Expansion into other form-heavy specialties

Deployment Model

forMaD is designed to work alongside existing clinical systems without requiring a direct EMR integration. Physicians can use the web application directly, with options for institutional deployment as the product evolves.

• Direct physician access
  • A production web application with registration, terms, payment, physician profile and delegate access. Initial use does not depend on a direct EMR integration.
• Institutional deployment
  • Hospitals and departments may require privacy, security and digital review even when the product operates outside the EMR. forMaD is being prepared with the documentation and controls needed to support that process.

What Comes Next

1. Production launch
   • Move the MVP into a monitored Canadian production environment with accounts, billing, delegate access, operational support and hardened privacy controls.
2. Institutional readiness
   • Prepare the documentation and controls needed to support hospital privacy/security review where required.
3. Expand the model
   • Use oncology as the first wedge, then extend the workflow model into other form-heavy specialties.