{"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-record-release%3At-low%3Av1","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Amedical-secretaries-and-administrative-assistants-patient-record-release%3At-low%3Av1","canonical":"https://api.sb/founding-hypotheses/fh%3Amedical-secretaries-and-administrative-assistants-patient-record-release%3At-low%3Av1","pool":"https://api.sb/v1/founding-hypotheses"},"foundingHypothesis":{"id":"fh:medical-secretaries-and-administrative-assistants-patient-record-release:t-low: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-record-release","stableHash":"wcc:medical-secretaries-and-administrative-assistants:patient-record-release:document:v1"},"problem":{"slotStatement":"When a lawyer, insurer, or patient's new provider faxes in a record request, the ROI coordinator has to decide — often in minutes, across a stack of scanned authorizations written on forms from five different acquired practices — whether the signer actually has authority to release the requested scope, whether the sensitive categories (psych notes, HIV, substance-use) are carved out correctly, and whether the release date window is still live; one wrong release sends PHI to an unauthorized party and the DSO eats an OCR investigation plus patient notification costs."},"approach":{"oneSentence":"An authority-boundary checker that reviews every inbound HIPAA authorization against the signer's legal standing (patient, personal rep with POA doc on file, guardian, subpoenaed party), redacts sensitive-category carve-outs the form didn't explicitly grant, and hands the ROI coordinator a reviewable disclosure packet with a per-field trace back to the specific authorization clause that permitted each released page."},"customer":{"icpShape":"PE-backed multi-site dental support organizations (company-type-pe-backed-dso) operating 15-80 practices across 2+ states, where the buyer is the DSO's VP of Compliance or Chief Compliance Officer who signs the tooling contract and carries HIPAA breach liability, and the daily user is the centralized Release-of-Information (ROI) coordinator or medical secretary processing patient chart requests across the practice portfolio.","beachheadShape":"EarlyAdopterJTBD: PE-backed DSO roll-ups that just absorbed 3+ acquired practices with inconsistent HIPAA authorization forms and are staring down a post-close OCR audit window."},"archetype":"startup-archetypes.org.ai/AgenticWorkflow-Subscription","beachhead":"EarlyAdopterJTBD: PE-backed DSO roll-ups that just absorbed 3+ acquired practices with inconsistent HIPAA authorization forms and are staring down a post-close OCR audit window.","competitors":{"substitutes":[{"name":"MRO Corp / Ciox Health (Datavant) outsourced ROI service","category":"incumbent","uncopyabilityReason":"MRO and Ciox are priced on a per-page BPO model where revenue scales with human reviewer headcount; shipping an authority-boundary autoreviewer that collapses their unit economics would cannibalize the contract structure PE-backed DSOs already signed them on. Deployment-mode-mismatch: they operate as an offsite service bureau with 48-72h SLA, not as an inbox-resident agent sitting inside the DSO's Dentrix/Open Dental practice management stack."},{"name":"ChartRequest","category":"incumbent","uncopyabilityReason":"ChartRequest is a requester-pays portal optimized for attorneys and insurers submitting requests; its integration depth into DSO-side practice management systems (Dentrix Enterprise, Denticon, Curve) is shallow because its economic buyer is the requester, not the DSO. Rebuilding a DSO-side authority-validation engine requires integration-depth work against dental PMS schemas and acquired-practice chart migration artifacts that ChartRequest has no commercial reason to invest in."},{"name":"Compliancy Group / HIPAA One","category":"incumbent","uncopyabilityReason":"These are annual HIPAA risk-assessment and policy-binder vendors — their liability-posture is advisory (they sell you a compliance program, not a per-release decision). Taking on real-time release-level authorization decisions would shift them from advisor to regulated decision-maker, a liability-posture flip their E&O coverage and business model do not support."},{"name":"Bookkeeper-style Google Sheet + scanned-authorization folder cross-check","category":"manual-bridge"},{"name":"Fax-and-call-the-practice-manager verification loop","category":"informal"}]},"studioThesis":"T-LOW","killThreshold":{"K":10,"M":40,"N":8,"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 ≥ 8/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Authority-boundary enforcement (does the tool decide who the signer legally is? advisory flagging only ↔ per-request authority determination with carve-out redaction before release)","yAxis":"Acquired-practice form heterogeneity handling (single-template assumption ↔ normalizes N legacy authorization templates from roll-up acquisitions into one decision surface)","winningQuadrant":"Per-request authority determination with carve-out redaction, running across heterogeneous legacy authorization forms inherited from acquired practices — so a PE-backed DSO CCO can point to a consistent release decision across all 47 sites regardless of which pre-acquisition form the patient signed.","loservilleEscape":true,"loservilleQuadrant":"Advisory-only flagging that assumes a single authorization template — where MRO/Ciox reviewers still hand-adjudicate every form variation offsite on a 72h SLA, and ChartRequest silently assumes a uniform requester-side template that breaks the moment a DSO's Dentrix chart contains a pre-acquisition paper authorization."}},"unmetRequirements":[],"pricingArchitecture":"single-price"},"actions":{},"options":{},"relationships":{"runtimeUnit":"https://api.sb/v1/runtime-units?startupRef=startup%3Afh%3Amedical-secretaries-and-administrative-assistants-patient-record-release%3At-low%3Av1","brand":"https://api.sb/v1/brands?startupId=startup%3Afh%3Amedical-secretaries-and-administrative-assistants-patient-record-release%3At-low%3Av1","listing":"https://api.services/listings?foundingHypothesisRef=fh%3Amedical-secretaries-and-administrative-assistants-patient-record-release%3At-low%3Av1","cell":"https://api.sb/v1/cells/work-contexts.org.ai/medical-secretaries-and-administrative-assistants-patient-record-release","thesis":"https://api.sb/v1/theses/T-LOW"},"meta":{"level":"L0","scopes":[]},"user":{"requestId":"a057bd4ccc0eb1a9","edgeLocation":"a057bd4ccc0eb1a9","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-record-release%3At-low%3Av1/references"},"items":[]}}