# JoltMed — product and delivery blueprint

A website, product map, and implementation handoff for the clinic infrastructure business.

## The promise

Everything a clinic needs to launch, run, and grow, under its own brand.

Three buying paths:
1. A single service or component.
2. A configured clinic with connected tools and clinical support.
3. An enterprise platform or service business serving other clinics.

This blueprint defines the intended product and delivery requirements. It does not certify that the underlying clinical, pharmacy, AI, payer, or payment integrations are live. The JoltMed marketing website and its proposal builder are separate from those clinical systems.

## Website delivered in this project

- A JoltMed homepage with a clinic workflow, solution categories, AI, pharmacy, clinical support, enterprise, ecosystem, and FAQs.
- 20 detailed service pages, each with inclusions, steps, purchase modes, questions, and service boundaries.
- Five enterprise product pages plus the enterprise overview.
- A brand ecosystem page for Telehealth US, Impact Health MD, TeleDocs, Impact Health X, and KinnectDr.
- A six-part presentation, patient journey, and implementation blueprint.
- A plan builder with selected modules, delivery preference, and a project brief.
- An inquiry page that prepares an email to contact@telehealthus.com for the visitor to review and send. It does not silently submit leads or claim that an email has been delivered.
- Responsive navigation, per-page titles, a branded favicon, and a useful not-found page.

The selected JoltMed domain remains a separate ownership and DNS task. A hosted Sites address is the review address until a custom domain is connected.

## Product catalog

### Clinical and trust

1. LegitScript support: readiness review, gap closure, actual clinical relationships, credential documentation, application coordination, reviewer responses, renewals.
2. Insurance enablement: clinical entity mapping, group relationship review, provider credentialing and enrollment, payer effective dates, eligibility, claims, remits, denials.
3. Medical directors and collaborators: role matching, state and specialty fit, contracts, protocols, chart review, escalation and supervision responsibilities.
4. Provider staffing: licenses, availability, visit types, clinical entity, volume, schedules, escalation and onboarding.
5. PC and MSO support: clinical practice relationship, entity formation coordination, state registrations, agreements and operating responsibilities with qualified counsel.
6. Clinical Authority packages: accurate bios, real clinical roles, approved credentials and photos, review attribution, structured page content, update ownership.

### AI and automation

7. AI patient intake: text and voice, approximately eight core questions for a simple pathway, adaptive follow-ups, source answers, review, consents, draft SOAP note and clinician routing.
8. AI scribe and notes: standard form answers, AI intake, or consented visit transcript to a draft; clinician edits and signature; supported EHR writeback or export.
9. Language and translation: text and audio, language preferences, original and translated views, qualified interpreter handoff and verification of important instructions.
10. AI voice agents: inbound receptionist, permission-based outbound follow-up, intake and consent reminders, administrative refill collection, staff transfer, approved knowledge and scripts.
11. Website chat and voice: branded widget, approved knowledge, scheduling and portal navigation, text or voice choice, human handoffs.

### Clinic technology

12. EHR and practice management: forms, consent versions, schedules, patients, encounters, notes, tasks, roles, practice reports, brand workspaces.
13. Websites and patient funnels: service pages, clinician information, booking, intake, portal navigation, approved campaign pages, privacy-reviewed measurement.
14. Pharmacy marketplace: participating partners, catalog and quote versions, formulation attributes, state and delivery eligibility, appropriate ordering, fulfillment events and exceptions.
15. Payments and connected accounts: approved merchant setup, explicit seller and services, checkout, recurring billing, refunds, payouts, reconciliation.
16. Labs and care coordination: eligible testing, authorized orders, result routing, assigned clinical review, patient follow-up and exception handling.

### Growth and community

17. Marketing: approved Google and Meta campaigns, service pages, funnels, search content, opt-in email and text, performance reporting.
18. Affiliate marketplace: reviewed program structure, approved partners, unique links, non-PHI attribution, commissions under permitted terms, refund adjustments and payouts.
19. Memberships: explicit benefits, recurring billing, renewals, cancellation, member access, reporting and scope of included care.
20. Communities and creator tools: professional groups, moderated patient education, creators, posts, videos, events, courses, podcasts, discovery, booking and paid nonclinical sessions.

## Enterprise offers

| Offer | Customer experience | Delivery foundation |
| --- | --- | --- |
| Branded pharmacy marketplace | Own brand, own clinic network, eligible offers and orders | Confirmed pharmacy agreements and supported catalog/order/status connections |
| Multi-brand practice platform | Distinct clinic brands, staff, records and reporting | Shared platform with strict practice data separation and explicit authorized group access |
| Embedded AI suite | Intake, scribe, language, phone and web assistants inside another product | Narrow integration contracts, data permissions, validated models, safe human handoffs |
| Healthcare service business | Certification support, healthcare marketing, clinic launch services or insurance coordination under the buyer's brand | Real supplier capacity, written scope, onboarding guides, operating procedures and support |
| Insurance-enabled clinic network | A network with defined clinical entities, providers, payers and billing operations | Group arrangements, enrollment, confirmed effective dates and validated claims processes |

Prefer reusable infrastructure with configuration over rebuilding the same foundation for each enterprise. Isolate brands and accounts. Use a partner adapter layer so an upstream vendor change does not require rebuilding every clinic.

Proposed commercial structure: setup/integration fees, platform licenses or service subscriptions, contracted operational support, and permitted usage or transaction fees. Pricing, margins, pharmacy economics, medical management fees, and referral compensation require actual cost modeling, partner terms, and legal review. Do not treat per-prescription margin as automatically permitted.

## Patient journey and handoffs

1. Discover: patient sees an approved ad, clinic site, creator, or partner link. Public pages collect business or permitted lead information only; sensitive care details do not go to ad tools.
2. Prepare: patient selects a service, completes appropriate identity/state checks, chooses a language, types or speaks through intake, reviews the answers, and records required consent.
3. Connect: route to a qualified clinician and permitted visit type. Emergency flags have a clear urgent-care or emergency path. Do not treat a disclaimer as the entire escalation process.
4. Review: clinician reviews original intake data and any AI draft, evaluates the patient, and completes clinical decisions. Recording or scribe collection requires the appropriate consent.
5. Complete: clinician signs the note and authorizes any appropriate orders. The order goes only to an eligible pharmacy or lab. Payment or insurance workflow uses the correct entities and approvals.
6. Follow up: assign results review, clinical questions, reminders, refills and follow-up visits. Honor communication preferences. Keep community activity separate from the medical record unless explicitly and lawfully connected.

## Roles and access

- Patient: own forms, consents, encounters and permitted account details.
- Clinician: authorized patient records and clinical tasks; reviews, edits and signs notes; owns clinical decisions.
- Clinic staff: only assigned practice operations and role-appropriate information.
- Enterprise administrator: configured brands, permissions and authorized reporting. Enterprise ownership must not automatically expose every clinical record.
- Pharmacy or lab partner: minimum information for the authorized order and fulfillment.
- Affiliate or creator: own approved material, links and limited business reporting; no patient medical details.
- Support: time-limited and purpose-limited access, with an audit trail where patient systems are involved.

## Core architecture contracts

These are target integration contracts, not existing production API claims.

Identity and tenancy:
- Organization, clinical entity, brand, practice, location, user, role assignment.
- Every patient-facing record carries the appropriate practice and clinical entity context.
- Enforce authorization on the server; never rely only on a selected brand in the UI.

Care records:
- Patient, form version, intake session, source answers, consent receipt, appointment, encounter.
- Draft note, source transcript, language mapping, clinician edits, signed note version.
- Order, laboratory result, pharmacy fulfillment status, follow-up task.

Commercial records:
- Merchant approval scope, connected account, checkout, payment, refund, payout and reconciliation event.
- Payer, provider enrollment, group affiliation, effective date, eligibility response, claim and remit.
- Approved affiliate agreement, link attribution, eligible event, commission decision and payout.
- Membership, recurring consent, benefit entitlement, renewal and cancellation.

Example event contracts:
- intake.completed: practice ID, session ID, form version, consent reference, timestamp.
- note.draft_created: encounter ID, source references, generation version, review status.
- note.signed: encounter ID, clinician ID, immutable version, signature timestamp.
- appointment.booked: patient and provider references, authorized service/state, schedule reference.
- order.authorized: order ID, prescriber, entity, destination, exact formulation, source encounter.
- order.status_changed: partner order ID, version, status, event timestamp, safe exception details.
- payment.updated: processor event ID, seller/entity, amount, currency, status, original transaction reference.
- membership.canceled: membership ID, requested date, effective date, billing stop status.

All incoming partner events require authentication, schema validation, deduplication, idempotent processing and auditable failure handling. Retries must not duplicate orders, charges, payouts or outreach. Assign an owner to unresolved exceptions.

## Component delivery requirements

### Pharmacy marketplace
- Confirm participating pharmacies and actual licensed destinations.
- Normalize medication, strength, concentration, form, quantity, package and storage/shipping requirements without falsely equating different formulations.
- Distinguish patient-specific prescriptions from office-use supply.
- Display partner source, quote time, expiration, stock and shipping assumptions.
- Prevent ineligible orders; require appropriate clinical authorization.
- Scope partner adapters individually. Do not promise live connections without validation.
- Keep a documented exception process for unaccepted, delayed or canceled orders.

### AI intake and scribe
- Confirm intended patient population, allowed services, question flow and escalation.
- Treat three-to-five-minute intake as a design target, not an observed performance guarantee.
- Preserve original answers and identify source information.
- Do not generate unsupported exam findings, completed diagnoses, or treatment decisions.
- Keep draft and signed states distinct. Only authorized clinicians finalize notes.
- Evaluate representative and edge cases, including incomplete answers, language mismatch and urgent concerns.
- Confirm processing agreements, retention, access and model use before patient information flows.

### Voice and website assistants
- Version the approved knowledge and scripts.
- Separate education, administrative tasks and clinical advice.
- Confirm outreach consent, recording requirements, number routing, suppression and opt-outs.
- Limit write actions to approved workflows.
- Define staff transfer, callback and emergency paths.
- Test failed transfers, interrupted calls and unavailable downstream systems.

### EHR and enterprise
- Isolate practice data; test unauthorized cross-practice requests.
- Scope external connections based on real documentation and granted permissions.
- Make scheduling conflicts and data conflicts visible.
- Preserve signed note versions and access audit records.
- Define import/export and migration checks.
- Document backup, recovery, incident response and support before clinical deployment.

### Insurance and payments
- Identify the licensed treating entity, rendering provider and billing entity.
- Distinguish malpractice coverage, group affiliation, enrollment and payer contracts.
- Track payer effective dates and approved services.
- Confirm the payment processor's written service approval.
- Never use an approved connected account to disguise restricted or unapproved services.
- Verify signed processor events, refund behavior and reconciliation.
- Do not promise reimbursement or certification outcomes.

### Growth, affiliates and communities
- Keep patient health information out of advertising and affiliate reporting.
- Review referral compensation and permitted offers.
- Link conversions without revealing clinical details.
- Reconcile returns and refunds before payouts.
- Display clear membership terms and cancellation controls.
- Separate medical care from creator content and education.
- Moderate groups and validate professional credentials where represented.

## Launch gates and delivery order

Stage 1 — Offer and operations:
Name the actual service owner, legal/clinical entities, suppliers, pricing assumptions and fulfillment responsibilities. Confirm the offer can be delivered.

Stage 2 — Patient and practice foundation:
Implement identity, practice boundaries, permissions, intake, consent, scheduling and clinical note review. Test the patient path with non-production test records.

Stage 3 — Partner connections:
Validate the actual EHR, pharmacy, lab, processor and payer connections included in the scope. Use retry-safe events and operational exception queues.

Stage 4 — AI and outreach:
Evaluate outputs, consent, urgent concern routing, human handoffs, translation limits and communication preferences. Confirm traceability to source records.

Stage 5 — Enterprise:
Test brand and tenant separation, customer clinic onboarding, support procedures, usage reporting, commercial rights and account closure/export.

A release is ready only when:
- The patient can complete the intended journey.
- Authorized people can do their tasks and unauthorized people are denied.
- A note cannot silently move from draft to signed.
- Failed integrations have a visible recovery path.
- Orders, charges and messages are not duplicated.
- Required suppliers, approvals, agreements and effective dates are confirmed.
- A named owner handles ongoing exceptions and support.

## Open decisions to resolve with the delivery team

- Who owns and controls joltmed.com, and where should DNS point?
- Which branded platform modules are actually ready, and what evidence confirms each one?
- Which pharmacies, labs, EHRs, phone and AI vendors have signed agreements and supported integrations?
- Which clinic services, states, provider types and hours are available at launch?
- What are the service-level expectations and escalation contacts?
- What pricing and unit costs support each package?
- What enterprise branding, IP, data, support and resale rights are granted?
- Which payment models, payer relationships and compensation structures are approved?
- What is the data retention and deletion policy for each clinical component?

## Public wording to preserve

- Certification preparation and coordination, not guaranteed certification.
- Real and authorized clinical credentials, not borrowed credibility.
- National expansion planning with verified coverage, not every service guaranteed in every state.
- Fast-start staffing assessment, not unconditional 24-hour coverage.
- Provider-reviewed AI drafts, not automated treatment decisions.
- Confirmed integration scope, not “works with every EHR.”
- Processor-approved payments, not a workaround while certification is missing.
- Accurate clinical profiles, not guaranteed search rankings.
- Clearly described commercial models, not guaranteed earnings.

Official reference points:
- [LegitScript Healthcare Certification FAQs](https://www.legitscript.com/certification/healthcare-certification/faq/)
- [LegitScript Healthcare Certification Standards](https://www.legitscript.com/certification/healthcare-certification/)
- [Stripe restricted business policy](https://stripe.com/legal/restricted-businesses)
- [CMS provider enrollment](https://www.cms.gov/medicare/enrollment-renewal/providers-suppliers)

This brief is an implementation target and business handoff, not legal advice or proof of operational readiness.