Kno | bility

Clinical Decision Support

Your patient's complete record, from every place they have been seen, with their authorization.

Kno | bility does two separate jobs. First, it lets a practitioner find a patient across connected EHRs (interoperability), using the patient's identifying details and their care history: the hospitals, facilities and doctors they have seen. Kno | bility retrieves the C-CDA documents the patient has authorized (the standard clinical document templates for each kind of visit and encounter). The practitioner can review and search them, and copy what they need into their own note for the current visit. If the patient allows it, the practitioner may keep the records afterwards. Otherwise they are removed when the practitioner's session ends.

Second, as a longer-term service within Kno | bility, patients may opt in to having their records added to a de-identified knowledgebase: an anonymous care reference for population health, clinical decision support, care insights, peer review and outcomes analysis across the practitioner community. The two never mix. Nothing identified is ever published without the patient's authorization.

Practitioner sign inPatient sign inRead the guide

Primary product

Clinical Decision Support: patient records

Identified. For registered users, and only with the patient's authorization.

  • Practitioners register with a current NPI number, checked against the National Provider Identifier (NPI) Registry, the U.S. government registry of every healthcare provider. A Kno | bility user ID is assigned when registration is complete.
  • Patients register with their identifying details (name, date of birth, gender, address) and their existing EHR patient ID.
  • The patient names the hospitals, facilities and doctors they have seen. Each is matched to its EHR, and Kno | bility retrieves the records the patient has authorized from each one.
  • The patient decides what the practitioner may see before anything is retrieved.
  • Once the results are in, the patient decides whether the practitioner keeps a copy of all of them, or only their own note for this visit.
  • Without that authorization, the results end with the practitioner's session.

A service within Kno | bility

Clinical knowledgebase

Anonymous. Requires a Kno | bility account.

  • A clinical care reference for decision support, built from de-identified patient care information organized by C-CDA template.
  • Records are included only when the patient opts in.
  • Practitioners and patients each have their own set of capabilities.
  • Search by medical and clinical attributes, including population-level analysis by diagnosis and treatment terms and codes.
  • Credentialed peers endorse or challenge every insight.
Care insights
24
Peer reviews
45
Contributing nodes
8
Verified contributors
10

Clinical Decision Support walkthrough

Five steps for the practitioner at the point of care. These pages need a practitioner sign-in.

  1. 1

    Find a patient

    Search by name, date of birth and gender. The patient is found first in your own EHR, to confirm who they are.

    Open →
  2. 2

    Patient authorization

    The patient decides what you may see, for how long, and whether you may keep a copy afterwards.

    Open →
  3. 3

    Practitioner directory

    The patient names the hospitals, facilities and doctors they have seen. Each is looked up in the national NPI Registry and matched to the EHR that holds their records.

    Open →
  4. 4

    Session records

    The authorized clinical documents (C-CDA) from every matched EHR, in one place. Filter and search them by section and field.

    Open →
  5. 5

    Record composition

    Start a note for today's visit from a C-CDA template, copy in what you need from the results, then save it as a PDF.

    Open →

The knowledgebase in five principles

Decentralized

Every participating organization runs its own node. Case notes are read, parsed and stripped of identifiers where they already live. Nothing identified is ever sent anywhere, because there is no central store to send it to.

Fully anonymous

The unit of storage is an insight, not a person. There is no patient entity in the knowledgebase and no lookup table behind the case references. Cohorts are checked for re-identification risk before they can be published at all.

Peer-reviewed

Credentialed clinicians endorse, refine or challenge every contribution. Consensus is scored and shown. Contested insights stay visible and stay marked contested, because hiding disagreement is how a knowledgebase rots.

Real-world, real-time

Not a textbook. What was actually done, in how many cases, across how many organizations, and what followed. Each insight carries its own stated limitations.

For practitioners and patients

Clinicians describe the case in front of them and get ranked reference with safety signals that cite their sources. Patients read the same knowledge in plain language and leave with better questions.

Knowledgebase: where the de-identification boundary sits

Everything to the left of the dashed line stays inside the organization that produced it. Only what is to the right of it exists on the network.

INSIDE THE NODE - IDENTIFIED DATA NEVER LEAVESNODE BOUNDARYTHE NETWORK - ANONYMOUS KNOWLEDGE ONLYLocal case notesC-CDAPDF and OCRHL7 v2 / XMLPlain textNames, MRNs, dates,addresses.De-identificationNames removedMRNs removedDates reduced to yearAddresses generalizedAges over 89 bandedk-anonymity checkedTreating practitioners are kept:a provider is not a patient identifier.Care insightCohort, not a personPresentationInterventionOutcome observedReal-world signalStated limitationsAn anonymous case reference thatresolves to nobody, by design.Peer reviewCredential verifiedEndorseRefineChallengeConsensus scoredStatus publishedContested insights stay visible,marked as contested.Practitioner consultDescribe the case in front of you.Get ranked real-world referenceand safety signals that cite theinsights they stand on.Patient knowledgeThe same knowledge in plainlanguage, with no account andno record kept of the reader.Questions worth asking.The dashed line is the whole product. To the left, care as it is actually delivered, with every identifier intact. To the right, only what was learned.In this MVP every stage runs in the browser against fabricated data. Nothing is transmitted, and the de-identification stage genuinely runs.

Knowledgebase walkthrough

Six steps, in order. These pages need a sign-in. For a hands-on run through patient records, follow the guide.

  1. 1

    Watch identifiers being destroyed

    Twelve case documents are waiting in the local queue. Open one and see the real names, record numbers and dates beside the redacted output the network actually receives.

    Open local ingestion →
  2. 2

    Ask before the knowledge exists

    Run the atrial fibrillation consult now. The network has almost nothing to say, and it tells you that rather than inventing a warning.

    Run a consult →
  3. 3

    Process the queue

    Six stages per document, ending at a k-anonymity check. Insights only publish once every document behind them has been processed.

    Process the queue →
  4. 4

    Ask the same question again

    The same consult now returns ranked insights, aggregate real-world signal, and safety signals that name the insights they stand on.

    Re-run the consult →
  5. 5

    Disagree with something

    The review queue holds the contested and under-review insights. One of them is being argued about by two reviewers right now.

    Open the review queue →
  6. 6

    Read it as a patient

    Sign in as a patient to read the same knowledge in plain language, with the questions it suggests you ask.

    Open the patient view →

What this build is, and what it is not

An internal demonstration. Read this before relying on anything you see.

It is

  • A functional front-end MVP of the whole journey, from registration to sign-out.
  • A real de-identification engine. It genuinely scans and redacts the 18 case documents in this repository.
  • A real retrieval and safety engine that refuses to emit an uncited signal.

It is not

  • Connected to any real EHR, node, network or backend. The EHRs are simulated in the browser.
  • A clinical reference. Every insight is fabricated for demonstration.
  • Holding any real patient information. Every patient, record and practitioner is invented.