{"api":{"name":"api.sb","description":"Business-as-Code surface for Startups.Studio","home":"https://api.sb","docs":"https://api.sb/docs","version":"1.0.0"},"$context":"https://api.sb/$context","$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Amedical-secretaries-and-administrative-assistants-patient-intake-coordination%3At-td%3Av1","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Amedical-secretaries-and-administrative-assistants-patient-intake-coordination%3At-td%3Av1","canonical":"https://api.sb/founding-hypotheses/fh%3Amedical-secretaries-and-administrative-assistants-patient-intake-coordination%3At-td%3Av1","pool":"https://api.sb/v1/founding-hypotheses"},"foundingHypothesis":{"id":"fh:medical-secretaries-and-administrative-assistants-patient-intake-coordination:t-td:v1","lens":"AgenticWorkflow","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":1,"C7_magicLensFit":1,"C4_competitorHonesty":1,"C6_crossSlotCoherence":1,"C1_customerSpecificity":1,"C2_problemFrictionRealism":1,"C9_killCriteriaAttestability":1,"C3_approachEngineCoverability":1,"C5_differentiationLoservilleEscape":1},"upperRightLoserville":true},"cellRef":{"id":"work-contexts.org.ai/medical-secretaries-and-administrative-assistants-patient-intake-coordination","stableHash":"wcc:medical-secretaries-and-administrative-assistants:patient-intake-coordination:multimodal:v1"},"problem":{"slotStatement":"Intake coordinators routinely cross the authority boundary during pre-visit prep — confirming prior-auth codes, promising procedure dates, or swapping medications on the patient's behalf — based on a forwarded email from the clinic that never actually came from a credentialed clinician, and the agency owner only discovers the unauthorized action weeks later when a payer clawback or a state-board complaint lands."},"approach":{"oneSentence":"Every pre-visit action the coordinator is about to take — prior-auth submission, procedure scheduling, med-list edit, referral dispatch — gets routed through a standing-order boundary check that matches the action against the clinician-of-record's signed scope and produces a traceable record of who authorized what, so the agency owner can show the clinic (or a payer auditor) a clean chain of authority instead of an email thread."},"customer":{"icpShape":"Operations lead at a 6-25 person bootstrap agency (company-type-bootstrap-agency) that white-labels patient intake coordination for 3-12 independent specialty clinics (derm, ortho, GI), where the buyer is the Agency Owner/Managing Partner who signs the contract and owns HIPAA BAA exposure, and the daily user is the Lead Intake Coordinator running pre-visit prep queues across client clinics.","beachheadShape":"EarlyAdopterJTBD: bootstrap intake-coordination agencies whose clinic clients just failed a payer audit on prior-auth documentation or got burned by a coordinator auto-scheduling a procedure outside the clinician's standing-order scope."},"archetype":"startup-archetypes.org.ai/AgenticWorkflow-MarketplaceClearing","beachhead":"EarlyAdopterJTBD: bootstrap intake-coordination agencies whose clinic clients just failed a payer audit on prior-auth documentation or got burned by a coordinator auto-scheduling a procedure outside the clinician's standing-order scope.","competitors":{"substitutes":[{"name":"Ad-hoc approval email threads between coordinator and clinic office manager","category":"informal"},{"name":"Forwarded 'ok to schedule' texts from clinician cell phones","category":"manual-bridge"},{"name":"Phreesia (patient intake SaaS)","category":"incumbent","uncopyabilityReason":"Phreesia's integration depth is built around in-clinic kiosk and registration flows owned by the clinic itself — it has no concept of a third-party coordination agency acting under a delegated standing order, and adding an authority-boundary layer would require re-architecting its per-clinic tenant model to support agency-as-middle-actor with per-clinician scope attestations. That is an integration-depth barrier its existing clinic-direct deployment cannot absorb in 6 months."},{"name":"Athenahealth athenaOne patient workflow","category":"incumbent","uncopyabilityReason":"Athena's revenue model is locked to clinic EHR licensing and its regulatory/liability posture assumes the acting user is the clinic's own credentialed staff under the clinic's own compliance program. Extending to agency coordinators operating under a BAA across multiple unrelated clinics would force Athena to take on liability-posture risk it has spent a decade explicitly disclaiming in its MSAs — a liability-posture barrier, not a feature gap."},{"name":"Zapier/Make + ChatGPT intake automations stitched by the agency itself","category":"AI-native horizontal","uncopyabilityReason":"Horizontal LLM-plus-automation stacks have no vertical-data corpus of specialty-specific standing orders (derm Mohs protocols, ortho injection scopes, GI prep formularies) and no way to bind a coordinator action to a specific clinician's credentialed scope-of-practice. Closing that gap requires building a vertical-data corpus of clinician scope attestations per state board — a barrier orthogonal to LLM quality."},{"name":"Salesforce Health Cloud patient coordination module","category":"incumbent","uncopyabilityReason":"Health Cloud's distribution channel is enterprise IDN and payer accounts with 9-12 month implementations and 6-figure ACVs; a 12-person bootstrap agency cannot transact with Salesforce's field sales motion and Salesforce cannot profitably service that segment — a distribution-channel barrier that makes the bottom-of-market agency segment structurally unreachable."}]},"studioThesis":"T-TD","killThreshold":{"K":10,"M":70,"N":7,"rubricItemSet":["C1_customerSpecificity","C2_problemFrictionRealism","C3_approachEngineCoverability","C4_competitorHonesty","C5_differentiationLoservilleEscape","C6_crossSlotCoherence","C7_magicLensFit","C8_lensFit","C9_killCriteriaAttestability"],"verdictPolicy":"all-load-bearing-pass-and-overall-ge-X","loadBearingItemSet":["C1_customerSpecificity","C2_problemFrictionRealism","C3_approachEngineCoverability","C4_competitorHonesty","C5_differentiationLoservilleEscape","C6_crossSlotCoherence","C9_killCriteriaAttestability"],"verdictPolicyVerbatim":"KILL unless every load-bearing rubric item passes per workbook AND overall pass-rate ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Authority boundary enforcement (coordinator acts on forwarded-email trust ↔ every action matched against a signed clinician scope-of-practice attestation)","yAxis":"Actor topology (single-clinic staff inside one EHR tenant ↔ third-party coordination agency spanning many independent clinics under BAA)","winningQuadrant":"Per-action scope-of-practice matching designed natively for an agency coordinating across many unrelated clinics, so the agency owner gets a defensible authority trail without asking each clinic to change its EHR.","loservilleEscape":true,"loservilleQuadrant":"Email/text-forwarded 'ok to proceed' approvals inside a single-clinic tool like Phreesia or athenaOne, where the agency coordinator's action is neither bound to a named clinician's scope nor portable across the clinic portfolio — the documented failure mode behind payer clawbacks and state-board complaints on unauthorized pre-visit actions."}},"unmetRequirements":[],"pricingArchitecture":"tiered"},"actions":{},"options":{},"relationships":{"runtimeUnit":"https://api.sb/v1/runtime-units?startupRef=startup%3Afh%3Amedical-secretaries-and-administrative-assistants-patient-intake-coordination%3At-td%3Av1","brand":"https://api.sb/v1/brands?startupId=startup%3Afh%3Amedical-secretaries-and-administrative-assistants-patient-intake-coordination%3At-td%3Av1","listing":"https://api.services/listings?foundingHypothesisRef=fh%3Amedical-secretaries-and-administrative-assistants-patient-intake-coordination%3At-td%3Av1","cell":"https://api.sb/v1/cells/work-contexts.org.ai/medical-secretaries-and-administrative-assistants-patient-intake-coordination","thesis":"https://api.sb/v1/theses/T-TD"},"meta":{"level":"L0","scopes":[]},"user":{"requestId":"a057bd6049b13488","edgeLocation":"a057bd6049b13488","geo":{"country":"US"},"ua":{"browser":"Claude"}},"references":{"total":0,"limit":25,"page":1,"links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Amedical-secretaries-and-administrative-assistants-patient-intake-coordination%3At-td%3Av1/references"},"items":[]}}