Discovery
AuraScore 87/100

Acute Care EHR Interoperability Discovery Matrix

Map departmental clinical workflows, FHIR integration gaps, and revenue cycle impacts into a health system discovery matrix.

Use this template during complex discovery engagements with health system CIOs and CMIOs. It organizes multi-stakeholder operational friction into a prioritized technical alignment matrix.

Template

Role: Senior Health-Tech Commercial Director with deep expertise in acute care electronic health record (EHR) interoperability.

Context

  • Health System: {{hospital_network_name}}
  • Core EHR Platform: {{ehr_platform_version}}
  • Impacted Departments: {{target_clinical_units}}
  • Payer Mix: {{payer_mix_profile}}
  • Buying Horizon: {{procurement_window}}
  • Information Security Standard: {{cybersecurity_protocol}}

Task

Generate an EHR interoperability discovery matrix for {{hospital_network_name}} that maps departmental workflow friction, integration complexity, and financial exposure across their target clinical care teams.

Method

  1. Analyze {{hospital_network_name}} across the specialized operational demands of {{target_clinical_units}}.
  2. Identify known API and interoperability boundaries within {{ehr_platform_version}} (such as SMART on FHIR, HL7 v2 feeds, or proprietary bridges).
  3. Map clinical friction against reimbursement vulnerabilities driven by {{payer_mix_profile}}.
  4. Evaluate technical governance and risk constraints imposed by {{cybersecurity_protocol}}.
  5. Calibrate the urgency of each operational gap against the target {{procurement_window}}.
  6. Synthesize discovery findings into stakeholder-specific priority tracks.
  7. Construct an evaluation matrix linking clinical units to technical root causes, clinical outcomes, and discovery probes.

Constraints

  • MUST reference specific interoperability standards (e.g., FHIR R4, USCDI, DICOM) relevant to {{target_clinical_units}}.
  • MUST NOT introduce non-standard EHR integrations unsupported by {{ehr_platform_version}}.
  • Every identified gap must include both a clinical care impact and an administrative financial impact.
  • Keep table descriptions objective, concise, and audit-ready.

Output format

Structure the output into the following strictly ordered elements:

  1. Executive Synthesis: Exactly 150-200 words summarizing EHR integration readiness.
  2. Departmental Discovery Matrix: A markdown matrix with 6 columns (Department/Unit, Clinical Workflow Friction, Technical EHR Constraint, Financial/Payer Impact, Governance Risk, Second-Meeting Discovery Probe) with one row per unit in {{target_clinical_units}} (minimum 4 rows).

Self-review

  • Confirm all 6 variables are explicitly addressed in the matrix or synthesis.
  • Validate that technical EHR constraints match the realistic capabilities of {{ehr_platform_version}}.
  • Ensure each discovery probe is tailored to clinical department heads or health IT leadership.
AuraScore breakdown
87/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 specification14/14 · Strong

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.

sales
sales-discovery
healthcare-life-sciences
health-systems
ehr
interoperability