# SCRIMED Pilot Activation Planner Brief Status: pilot-activation-planner-active-synthetic-no-customer-go-live-authority Updated: 2026-07-09 Activation steps: 9 Activation plans: 5 Blockers: 6 Handoffs: 4 ## Boundary SCRIMED Pilot Activation Planner turns synthetic pilot value evidence into review-gated activation plans, prerequisites, owners, blockers, handoffs, and success criteria. It does not authorize live PHI, autonomous clinical care, diagnosis, treatment, prescribing, patient outreach, payer submission, EHR writeback, final imaging interpretation, production deployment, customer activation, certification claims, audited financial reporting, valuation assurance, revenue guarantees, profit guarantees, ROI guarantees, binding commercial offers, or legal/procurement approval. This brief is synthetic-only pilot activation planning. It does not authorize live PHI, autonomous clinical care, diagnosis, treatment, prescribing, patient outreach, payer submission, EHR writeback, final imaging interpretation, production deployment, customer activation, certification claims, audited financial reporting, valuation assurance, revenue guarantees, profit guarantees, ROI guarantees, binding commercial offers, or legal/procurement approval. ## Activation Plans - Workflow discovery activation plan: Move a buyer from demo interest to a 30-day no-PHI workflow discovery assessment. Boundary: Not live clinical care, audited savings, staffing reduction guarantee, or customer activation. Next: Create buyer-specific workflow discovery packet and schedule human-reviewed scope call. - RCM documentation activation plan: Translate prior authorization and denial-review evidence into a review-gated RCM readiness pilot. Boundary: No payer submission, claim submission, coverage determination, reimbursement guarantee, or payment assurance. Next: Attach buyer policy examples as synthetic metadata requirements, not live payer submission instructions. - Patient access activation plan: Turn referral and follow-up evidence into a no-outreach patient access pilot plan. Boundary: No patient outreach, appointment scheduling command, care-plan modification, or patient-specific medical advice. Next: Prepare accessibility-aware synthetic journey demos for the buyer's care coordination lane. - Interoperability discovery activation plan: Convert integration complexity into metadata-only discovery, approval blockers, and technical owner mapping. Boundary: Not production connector approval, EHR writeback, raw schema review, or live PHI authorization. Next: Create a buyer-specific interoperability discovery worksheet. - Investor diligence activation plan: Turn proof routes, buyer evidence, risk controls, and milestones into claims-safe investor diligence support. Boundary: Not securities material, valuation assurance, investment advice, certification, or customer activation approval. Next: Prepare claims-safe investor appendix with validation commands and proof routes. ## Activation Steps - Qualified buyer intake validation (ready-for-scope, synthetic-only): Named buyer sponsor, use case, audience, timeline, and no-PHI pilot intent. Review: Founder review required before pilot scope is prepared. - Evidence packet selection (review-gated, synthetic-only): Buyer has selected a workflow, RCM, patient access, interoperability, or investor evidence packet. Review: Delivery lead confirms the packet matches the buyer problem before external sharing. - Non-binding pilot scope draft (review-gated, synthetic-only): Buyer confirms pilot window, team availability, and acceptable synthetic/no-PHI boundaries. Review: Qualified review required before sending any scope, pricing, or legal-adjacent language. - Security and privacy review packet (external-approval-required, external-approval-required): Buyer security contact, questionnaire path, data classification, and deployment expectation. Review: Security reviewer approves packet before buyer security distribution. - Data governance boundary confirmation (blocked-before-live, protected-sandbox-planning): Buyer confirms no live PHI and no raw connector payloads will be provided for this pilot phase. Review: Data governance owner approves before any artifact crosses organizational boundary. - Clinical governance boundary confirmation (blocked-before-live, external-approval-required): Buyer clinical sponsor accepts decision-support-only, reviewer-gated, no-live-care pilot mode. Review: Clinical reviewer approves all clinical-facing language before sharing. ## Blockers - Buyer has not named a sponsor, reviewer, security contact, or implementation owner. (high): Hold activation in discovery and request owner mapping before any scope language is sent. Release requirement: Named owners and meeting cadence. - Buyer requests live PHI, raw payloads, or production records before approval path is complete. (critical): Use synthetic fixtures, metadata-only discovery, or de-identified examples after qualified review. Release requirement: Approved data governance path, BAA/contract controls if applicable, and protected workspace evidence. - Buyer wants diagnosis, treatment, prescribing, triage, or clinical action authority. (critical): Keep the pilot decision-support-only and route live-care expansion to clinical authority readiness. Release requirement: Clinical governance signoff, validation evidence, and retained human final authority. - Buyer wants payer submission, claim submission, or coverage determination. (critical): Offer documentation completeness review and draft packet QA without submission. Release requirement: Human approval workflow and payer action authorization outside this public planner. - Buyer wants live connector, EHR writeback, PACS/RIS/HIS writeback, or production integration. (critical): Run metadata-only interoperability discovery and keep writeback blocked. Release requirement: External technical approval, security review, connector contract, and protected activation evidence. - Buyer or investor asks for guaranteed ROI, revenue, profit, valuation, certification, or binding commercial approval. (high): Use measurement-framework, readiness, and claims-safe language with qualified review. Release requirement: Qualified finance/legal review and evidence-backed language. ## Handoffs - Scope call handoff: Human-reviewed pilot scope call agenda. Review before send: Founder or delivery lead approval required before external send. - Security review handoff: Security/privacy packet for qualified buyer review. Review before send: Security owner approval required before distribution. - Implementation kickoff handoff: No-PHI kickoff plan and reviewer matrix. Review before send: Implementation lead approval required before scheduling or messaging. - Success review handoff: Claims-safe success review packet. Review before send: Qualified reviewer approval required before buyer or investor distribution. Next best move: Choose the buyer segment, attach the matching evidence packet, confirm owners, run the blocker checklist, and prepare a human-reviewed kickoff agenda before any external commitment.