Start a program

The intake is the account review

Contracting goes fast when these 37 questions have answers, and every one of them exists because a program somewhere went wrong without it. Work through the six phases — check off what you can answer today, and whatever is left unchecked is the agenda for the first call. Your progress saves in this browser, and the whole worksheet prints cleanly for the people who need to weigh in.

0 / 37 answered

Phase 01 · 6 questions

Who is contracting

The entities, the numbers, and the billing pathway. Nothing downstream can be designed until these are fixed.

Legal entity name and structure — who signs the MSA and the BAA? Why we askContracts and the BAA execute against this, and it decides whose compliance program owns the monitoring program. Billing NPIs and TINs, per site. Why we askClaims run under these. Multi-TIN groups need the single-owner-per-episode rule mapped before the first enrollment, not after the first denial. Is any site an FQHC or RHC? Why we askIt changes the billing pathway — the G0511-to-individual-codes transition — and therefore the entire revenue model. States of operation, and licensure of everyone who will touch monitoring. Why we askResponse clocks cross state lines; licensure must cross with them. EHR and version. Why we askDecides the integration path: HL7v2, FHIR, or start with flat export and integrate later. Starting narrow is fine; not knowing is not. What care management do you bill today — CCM, PCM, BHI, TCM? Why we askRPM stacks with some of these and collides with others. The overlap map is how the predictable audit finding gets prevented at design time.

Phase 02 · 6 questions

Population and program selection

Which programs, for whom, at what honest scale.

Target conditions, ranked — which program goes first? Why we askThe first program should be the one with patient density and a motivated clinician, not the most ambitious one. Eligible patient count per condition, honestly estimated. Why we askKit orders, staffing ratios, and the revenue model all key off this one number. Optimism here becomes idle cuffs and missed projections. Payer mix: Medicare FFS, Medicare Advantage, Medicaid, commercial, uninsured. Why we askEach pays differently or not at all, and MA coverage varies by contract. The mix decides whether the program's economics survive. Language mix of the panel. Why we askMaterials, nudges, and PRO collection are configured per language on day one. Retrofitting language access is how programs quietly exclude. Connectivity profile: what share of the panel has a smartphone? Broadband? Why we askDecides the default kit — cellular-first or app-based. The demo preference is not the answer; the panel is. Who is the physician champion? Why we askPrograms without a named champion stall at threshold sign-off. This is the most predictive single answer on the page.

Phase 03 · 6 questions

Care model

Thresholds need owners, owners need clocks, and minutes need to come from somewhere real.

Who watches: your clinical staff, staff you will hire, or a monitoring service? Why we askManagement minutes must come from named humans under a defensible supervision arrangement. 'The platform watches' is not an answer a payer accepts. Named owner and response clock for every threshold class. Why we askThe platform will not activate time-critical thresholds without an owner and an acknowledged test page. Decide who owns what before go-live week. After-hours and weekend escalation path. Why we askDeterioration does not keep clinic hours. Unowned nights are how programs fail patients first and audits second. Which titration or management protocols exist today, on paper? Why we askEscalation pods work from standing orders; everything else routes to the prescriber. No written protocols means the pod model waits. Supervision model for clinical staff time. Why we askDetermines who may perform management time under whom, and what the claim line attests. Your MAC's read matters here. Expected panel size per monitoring FTE. Why we askAlert fatigue is a staffing ratio before it is a software problem. If this number is aspirational, thresholds will be tuned to protect staff instead of patients.

Phase 04 · 6 questions

Device intent

The kit is the policy — and several billing rules hide inside it.

Default kit per condition: cellular, app-based, or camera-based? Why we askMatch the connectivity profile from phase two, not the demo. Cellular-first is the default for a reason. Which brands and feeds: BodyTrace, Withings, PAP direct interfaces, Oura, Whoop, other? Why we askDirect manufacturer feeds, aggregators, and cellular devices carry different integration paths and different billable-versus-context defaults. Who supplies each device: the practice, the program, or a DME provider? Why we askIf DME supplies it, the device-supply code is not yours. This is the most common structural error in sleep programs, and it is decided here. Kit logistics: shipped to the patient, or handed out at the visit? Why we askIn-clinic handout makes the 99453 setup a human moment and the first transmission same-day. Shipping trades that for reach. Pick deliberately. Who chases returns, and what is the re-kit loop? Why we askDevice economics assume cycling. A cuff that retires into a drawer after one episode doubles your hardware cost per patient. Accessibility variants: stocked, or exception-ordered? Why we askLarge-type, voice guidance, and dexterity alternatives are kit decisions. Stocked means the accessible option ships day one; exception-ordered means it mostly never ships.

Phase 05 · 6 questions

Billing and compliance

You submit the claims; the platform produces the record that survives the look-back.

Who submits claims, and through what clearinghouse or billing service? Why we askGathermed is not a billing agent and does not touch claims. The platform produces the defensible line items; your billers submit them. Which MAC and locality? Why we askRates and several coverage reads are local. Every number in the calculator is a national average until this answer replaces it. Consent workflow: where, by whom, in which languages? Why we askConsent is per data category and versioned. Cost disclosure happens here too — the coinsurance number goes on the first page, not the last. Coinsurance disclosure and hardship policy. Why we askPart B coinsurance on a fixed income is real money. A program that surprises patients at collections loses them and deserves to. Who else might bill RPM, RTM, or overlapping care management for these patients? Why we askSingle-owner-per-episode is enforced structurally, but the collision map — other groups, other TINs, other programs — has to come from you. Who owns audit readiness? Why we askDefense packets generate per patient per month. Name the person who receives them and the cadence at which someone actually reads one.

Phase 06 · 7 questions

Integration, security, and success

The last mile: access, data movement, and what the program is held to.

Who signs the BAA, and who runs your security review? Why we askThe BAA executes before any production data moves — without exception. Naming the security contact now saves three weeks later. SSO / identity provider, or local accounts? Why we askAccess is role-scoped and logged; it needs your IdP or an explicit decision to run local accounts. EHR write-back at launch: notes, claims support, or none? Why we askScope creep here is the number-one go-live delay. Starting with none is a valid and common answer. White-label or Gathermed-branded patient surface? Why we askTenancy and app packaging decision. Sponsors and platform builders answer differently than clinics. Go-live target and enrollment ramp. Why we askLive in days, not quarters — but only once the phases above are answered. The ramp should match staffing, not enthusiasm. Which KPIs will the program be held to? Why we askSixteen-day transmission rate, control rate, response-clock performance, stratified reach. Pick them now, before the first month makes the choice for you. Who is the executive sponsor? Why we askContracting stalls without one. The sponsor is who unblocks every other question on this page.

What happens with the answers

These answers become the program design review: track and code selection per condition, kit specification, threshold ownership map, billing pathway confirmation, and the integration plan — the concrete documents contracting signs against. Nothing here is legal, coding, or billing advice; the billing-pathway answers get verified against your MAC and payer contracts during review.

Create the organization profile

Send this to account review

This creates your organization profile in Gathermed and opens the review. It sends the fields below plus your checklist progress — nothing else, and nothing about patients. Do not enter any patient information here. Patient records are created inside the platform after the BAA executes, never through this site.

Organization name *

Organization type

Primary contact name *

Contact email *

Organization NPI (optional)

States of operation

EHR and version

First condition program

Default kit intent

Estimated eligible patients

Medicare FFS share of panel, roughly (%)

Target go-live

Anything the review should know

Submits to the Gathermed platform over HTTPS with your checklist progress attached. No account is created for you, no cookie is set, and nothing is submitted until you press the button. After a successful submission you continue by signing in at care.gathermed.com, where your reference number connects this profile to your account. If the submission cannot reach the platform, the download button produces the identical payload to email instead.

Or begin onboarding directly Pick the first condition