Launches
AuraScore 79/100

Software as a Medical Device Clinical Adoption Launch Brief

Develop a commercial brief uniting clinical informatics, provider workflow, and payer economics for SaMD product launches.

Deploy this template when bringing regulated digital health, AI diagnostic, or SaMD software to market. It equips commercial teams to drive provider adoption by addressing EHR integration, CPT reimbursement pathways, and clinical champion enablement.

Template

Role: Principal HealthTech Commercialization Lead specializing in regulated Class II/III Software as a Medical Device (SaMD).

Context

  • Medical Device Name: {{device_name}}
  • Clinical Specialty: {{clinical_specialty}}
  • Regulatory Clearance Status: {{regulatory_pathway}}
  • Electronic Health Record (EHR) Ecosystem: {{ehr_integration_depth}}
  • Economic Buyer Persona: {{health_system_buyer_persona}}
  • Reimbursement & CPT Coding Strategy: {{reimbursement_cpt_code}}

Task

Generate an actionable go-to-market commercial brief for {{device_name}} that aligns clinical efficacy with hospital IT governance, reimbursement mechanics, and physician adoption pathways across target health systems.

Method

  1. Deconstruct the clinical decision-support workflow to highlight friction points resolved by {{device_name}} for {{clinical_specialty}} teams.
  2. Detail the economic value proposition using {{reimbursement_cpt_code}} to demonstrate tangible ROI and billable upside for {{health_system_buyer_persona}}.
  3. Formulate the technical feasibility narrative addressing {{ehr_integration_depth}} interoperability, data privacy, and hospital IT compliance.
  4. Design a targeted clinical pilot program framework designed to transition health systems from free proof-of-concept to recurring multi-department enterprise licenses.
  5. Outline a departmental champion enablement kit (Chief Medical Officer, Chief Medical Information Officer, Department Chair) with persona-specific adoption messaging.
  6. Structure the multi-channel provider acquisition plan, integrating peer-reviewed validation studies, digital detailing, and specialty association advocacy.
  7. Establish key leading and lagging commercial metrics spanning technical integration speed, daily active clinicians, and recurring license conversion rates.

Constraints

  • MUST directly address hospital cybersecurity and HIPAA/SOC2 governance alongside clinical messaging.
  • MUST NOT make diagnostic or predictive claims exceeding the validated boundaries of {{regulatory_pathway}}.
  • Economic models must show exact revenue or cost-reduction calculations based on {{reimbursement_cpt_code}}.
  • Keep implementation roadmaps grounded in real hospital IT procurement cycles (3 to 9 months).

Output format

Structure the brief into four distinct sections:

  1. Commercial Value & Regulatory Architecture (max 300 words summarizing clearance and positioning)
  2. Health System Persona Alignment Matrix (table comparing CMIO, CFO, and Department Chair needs and proof points)
  3. Clinical Workflow & EHR Implementation Blueprint (step-by-step 4-phase rollout guide)
  4. Economics & Pilot Conversion Strategy (financial model narrative and pilot exit criteria checklist).

Self-review

  • Confirm technical integration claims directly align with {{ehr_integration_depth}} capabilities.
  • Ensure the financial business case accurately leverages {{reimbursement_cpt_code}} codes.
  • Validate that all clinical claims strictly conform to the parameters of {{regulatory_pathway}}.
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

marketing
marketing-launches
healthcare-life-sciences
digital health
samd
healthtech