Straight answers,
with the reasoning shown.

ClinixBoost connects clinical evidence, coverage requirements, and expected costs so that oncology decisions are easier to understand, trace, and act on.

Today that takes the form of three capabilities: structured NCCN guideline reports and drug policy checks from clinical documentation, criterion-level clinical trial matching, and an oncology EHR that connects documentation, practice operations, and billing. Each can be used on its own or together.

Our longer-term direction is a shared, auditable decision record: the patient context, the supporting evidence, the coverage requirements, the expected costs, and what happened afterward, visible to everyone with a stake in the decision.

See the platform ↗

Four groups share a stake in every oncology decision: patients and families, oncology practices, health plans, and the technology partners whose systems carry the information between them.

Oncology practices and the teams that review treatment requests are the primary users of the platform today. Patients and families benefit indirectly, through clearer documentation and fewer unresolved coverage questions. Technology partners can embed trial matching in the systems care teams already use.

Direct patient-facing views of rationale, coverage, and expected cost are part of our vision and are not available today.

What this means for each group ↗

Partly. Guideline queries, guideline reports and drug policy checks, and clinical trial matching are in use with early partners. The oncology EHR has full workflow coverage but is not yet in production deployment.

Two prerequisites gate wider production use, and we will not represent otherwise: documented Business Associate Agreements with every service that handles protected health information, and a formal agreement covering commercial use of NCCN guideline content.

We are accepting early access partners who want to shape the platform with us.

Talk to us about early access ↗

Established systems were built for hospitals or for large practices with research infrastructure, and treat prior authorization as a documentation task that someone has to write up.

ClinixBoost is built for oncology, and it carries evidence through the workflow: the guideline section, version, and category behind a treatment travel with the documentation into the coverage request, with the reasoning shown.

We are also candid about what we do not have yet. Interoperability breadth, certification, and e-prescribing are gaps relative to mature systems, and practices should weigh them.

Either. The ClinixBoost EHR is a complete system: scheduling, patient management, clinical documentation, dictation, messaging, billing, and a patient portal.

Guideline queries and the guideline report workflow also work alongside any existing EHR. Guideline queries can be embedded through a single service call, and the report workflow accepts clinical notes by fax, email, or upload with no integration required.

Guideline queries and guideline reports cover more than 90 cancer types with dedicated NCCN guideline coverage.

• Hematologic: AML, B-cell lymphoma, CLL, CML, Hodgkin lymphoma, myeloma, MDS, MPN, T-cell lymphoma, Waldenström's
• Solid tumors: breast, NSCLC, SCLC, colon, rectal, pancreatic, HCC, prostate, bladder, ovarian, cervical, melanoma, head and neck, esophageal, gastric, renal cell, endometrial
• Pediatric: pediatric ALL, B-cell, CNS, Hodgkin, neuroblastoma, Wilms tumor
• Rare: amyloidosis, Castleman disease, histiocytic neoplasms, mastocytosis, neuroendocrine, occult primary

Coverage is updated as new NCCN guideline versions are released.

There are three ways to submit a note.

• Web upload: upload a PDF and see the report in the browser; a copy is sent by email.
• Fax: send clinical notes to the ClinixBoost fax number. Multi-patient documents are split, each is processed, and the report is returned by fax.
• Email: send notes as attachments. The same workflow applies.

Reports are returned in minutes. Each one shows what was extracted, which guideline sections apply, and where information is missing, so the reviewing clinician can confirm or correct it.

Yes. The drug policy check accepts any health plan's policy document and reads three kinds of criteria from it: general requirements that apply to any patient, indication-specific criteria such as diagnosis, line of therapy, and biomarker status, and exclusions.

No pre-configured plan templates are needed. Each criterion is listed in the report with the evidence found for it, or a note that it was not found.

Yes. Clinical trial matching accepts uploaded documents, typed notes, or a direct integration from your own systems. It extracts the eligibility-relevant facts, including diagnosis, biomarkers, lab values, staging, treatment history, and performance status, and screens trials from partner networks.

Where eligibility depends on information that is missing, it asks targeted questions and suggests answers drawn from the notes, with the confidence shown. The assessment returns a verdict for each criterion, met, unmet, or uncertain, with the rationale, a downloadable report, and a referral email to the trial coordinator.

Clinical trial matching in detail ↗

Speech is transcribed by a medical-domain speech recognition service. The transcript is then corrected and enriched with patient context from the record, such as demographics, current medications, and the active problem list, and drafted into a structured note.

The provider reviews and signs the note. Nothing enters the record without that review. Signed notes can be exported as PDF.

Yes. It is a standalone capability with no EHR integration required. Notes are submitted by fax, email, or upload, and reports are returned the same way.

That makes it suitable for IPAs, health plans, and billing services that want structured, evidence-referenced reports without adopting a new system.

Yes. Every record is scoped to a practice at the database level, so practices are isolated from one another by design. Within a practice, multiple clinic locations are supported for scheduling, patient management, and reporting.

Yes. Guideline queries are exposed as a single service endpoint with backend-to-backend authentication, so your system can call it without a user login. It accepts a plain-language question, an optional guideline domain, and optional patient context, and returns a cited answer as it is generated.

Ask for the integration documentation ↗

Not yet. FHIR and HL7 interoperability, ONC certification, e-prescribing, and insurance verification are on our medium-term roadmap. We consider their absence one of the larger gaps relative to mature EHR systems, and practices evaluating the EHR should factor it in.

The integration architecture has been researched and planned. Tell us if it is a blocker for your evaluation.

Every answer to a guideline query cites the specific guideline section, version, and NCCN category of evidence (1, 2A, 2B, or 3) that supports it. Answers are drawn from the retrieved guideline text, not from general knowledge. If the guideline does not address a question clearly, the answer says so.

The answer is a reference, not a decision. The clinician reviews the cited source and decides.

Software does the reading and drafting. It extracts the relevant facts from clinical documentation, retrieves the applicable guideline text, and drafts a structured answer or report with its sources attached.

A second, independent pass checks the extracted facts before they are used, and the same input always produces the same report.

People review and decide. Clinicians confirm or correct what was extracted, weigh the cited evidence, and make the treatment decision. Reviewers at health plans see the same cited basis. We use several language and speech services and choose each for the task; no clinical data is used to train them.

Many coverage denials happen not because the treatment is clinically wrong but because the request does not tie the treatment to guideline evidence in the form reviewers expect.

A report that names the guideline section, version, and category, alongside the patient-specific facts drawn from the notes, gives a reviewer what they need to decide on first review.

We are building formal outcome tracking and will publish verified results as they become available. Until then we present this as the expected effect of the mechanism, not as a measured result.

Commercial use of NCCN guideline content requires a formal agreement with NCCN. That agreement must be in place before any production deployment that involves NCCN content, and it is on our pre-production checklist.

We will not deploy commercially until this is confirmed.

The platform is built with HIPAA requirements as a first-order design constraint: practice-level data isolation, role-based access control, encrypted messaging and storage, and audit logging.

Full compliance requires more than architecture. It also requires signed Business Associate Agreements with every vendor that handles protected health information, formal security policies, breach notification procedures, and a completed risk assessment.

BAA verification with PHI-handling vendors is on our pre-production checklist and is not yet fully documented. We will not represent the platform as HIPAA compliant until that process is complete.

Several layers apply.

• Data isolation: every patient record is scoped to a practice at the database level.
• Authentication: industry-standard session tokens with limits and refresh, and role-based access control with granular permissions.
• Messaging: real-time messages are encrypted and connections are authenticated at the protocol level.
• In transit: all external communication uses HTTPS and TLS.
• At rest: database and cloud storage are encrypted.
• Audit logging: every data access and change is logged with user identity and timestamp.

Access is governed by role-based permissions enforced at the service level. Roles include system administrator, practice administrator, provider, nurse, front desk, billing, and patient (portal only).

ClinixBoost staff do not have access to patient records in any production environment. Access logs are kept for every record view and change.

Verification of BAAs with every third-party service in the PHI processing chain is a pre-production requirement we treat as non-negotiable. That verification is in progress and not yet complete.

We will not run the platform in production with real patient data until BAAs are confirmed and documented for every service involved.

Clinical notes and generated reports are stored in your practice's isolated database partition, encrypted at rest, and used only to provide the service to your practice. Voice recordings are processed during the session and are not kept beyond it.

Notes submitted for guideline reports are sent to third-party processing services for analysis; those services are part of the BAA verification described above.

We do not sell, share, or monetize patient data, and we do not use it to train models, ours or anyone else's.

Pricing is not yet published. We are in an early access phase and are shaping pricing with our first partners.

The planned model is a per-seat subscription for the EHR and guideline queries, and per-report or volume pricing for the guideline report workflow on its own.

Discuss pricing for your use case ↗

Access is not self-serve at this stage. Tell us about your organization, your primary use case, and your timeline, and we will schedule a conversation to understand your workflow before onboarding. We would rather confirm fit first than have you invest time in an evaluation that is not one.

Build with us ↗

We offer guided walkthroughs tailored to your role and use case. Self-serve trials are not available; given the clinical nature of the platform, a guided evaluation focused on your actual workflows is more useful than a time-limited login.

Oncology practices and health plans: use the form on the Build with us page, or write to our general inbox. Technology partners and integration questions: our partnerships inbox. Trial networks and research sites: our trials inbox. Existing users: support.

Patients and families: the platform is not patient-facing today. Your care team is the right place for questions about your treatment and coverage.

All the ways to reach us ↗