Skip to content ReleaseVezual Beta is in the Plugins Console
Start free

Healthcare

Find approved
operating procedures.

Retrieve current nonclinical procedures by service and location. Show the document version and responsible team, using synthetic requests for the pilot.

Explore use cases Talk to our team
Procedure lookup
An open procedure binder highlights the current version and connects it to a location and responsible team.

Find the current intake procedure and the team responsible.

Illustrative use case

01 / Use case guide

10 practical use cases.

Compare the data models behind everyday industry tasks, from finding records to following connections.

SQL Filter and calculate Vector Match similar meaning Graph Follow relationships Full-text Find words and phrases

Suggested model combination

Scroll across to compare all four models
Use case How the data models help SQL Vector Graph Full-text Source
Find referral service options A coordinator needs service locations matching an already approved referral. Vector matches service wording; SQL filters location and appointment availability; Graph links services to providers and sites for staff review.
Find available appointment slots An accepted referral is waiting for an appointment. SQL lists available slots for the required service; Graph connects the referral, service and booking request for scheduling staff.
Follow up unbooked referrals Referral staff need to find requests still waiting for a booking. SQL filters referrals by booking state and age; Graph connects each request to contact attempts and the responsible provider.
Check referral document completeness A referral is missing an attachment required by the receiving service. Full-text retrieves the service's submission instructions; Graph links the referral to attachments; SQL checks required document flags and submission dates.
Review insurance coverage details Registration staff need the latest eligibility and benefit response before a visit. SQL retrieves the latest payer response, including service coverage, deductibles, copayments and network differences, for registration staff.
Check prior authorization requirements Administrative staff need the payer's documentation checklist for a planned service. SQL selects the payer, service and current requirement version; Full-text retrieves the required document list for staff review.
Track prior authorization responses Staff need to see whether a request was approved, denied or returned for more information. SQL filters authorization responses by status and date; Graph connects each response to its request and requested supporting documents.
Check outstanding claim status Billing staff need the latest payer status for unpaid claims. SQL lists unpaid claims and response timestamps; Graph connects each claim to its status inquiries and payer replies.
Explain claim payment adjustments Billing staff need to understand why a claim payment differs from the billed amount. SQL retrieves adjustment amounts at claim and line level; Full-text finds the supplied reason codes and their published explanations.
Reconcile remittances with claims A remittance covers several claims and must be matched to the right accounts. Graph links remittances to claims and claim lines; SQL compares payments and adjustments with the recorded account balances.

Use the query interfaces you need, then connect their results through shared record IDs in your application.

Industry sources 8

These sources describe real industry workflows. The model combinations above are proposed OriginChainDB designs, not customer deployment claims.

  1. NHS England Digital — e-Referral Service
  2. NHS England Digital — Appointment slot issues within the NHS e-Referral Service
  3. NHS England Digital — Referring a patient - NHS e-Referral Service
  4. NHS England Digital — Directory of Services: creating and maintaining services
  5. Centers for Medicare & Medicaid Services — Operating Rules for Eligibility and Claims Status
  6. Centers for Medicare & Medicaid Services — CMS Interoperability and Prior Authorization Final Rule CMS-0057-F
  7. Centers for Medicare & Medicaid Services — Claim Status Request and Response
  8. Centers for Medicare & Medicaid Services — Health Care Payment and Remittance Advice

02 / A closer look

Finding the current intake procedure

A coordinator needs the intake procedure for a particular service and site. The same process has several names, an older document is still searchable, and responsibility has moved to another team. This demonstration uses synthetic requests and nonclinical procedures.

What makes it difficult

  1. 01

    Staff describe the same process in different ways.

  2. 02

    Retired procedures can appear alongside current versions.

  3. 03

    Service, site and process ownership need to stay connected.

Suggested approach

Filter by service, site and approval date

Search staff wording against approved procedures, then return the active version and its owner. Retired documents should be excluded from current guidance.

03 / Queries

What each data model does

Select a model to see the question it answers.

SQL · Find the facts

The question

Show the active intake procedure for this site.

Filter by site, service, approval status and effective date.

Explore SQL
Vector · Match the meaning

The question

Find the process for arranging a first appointment.

Match staff wording to approved operational guidance.

Explore Vector
Graph · Follow the connections

The question

Which team owns this service's intake process?

Link services, locations, procedures and accountable teams.

Explore Graph
Full-text · Find the exact wording

The question

Find the procedure that references form IN-014.

Locate exact form codes and wording in approved documents.

Explore Full-text

Use shared record IDs to combine results from the different query interfaces in your application.

04 / Implementation

How to build it

  1. STEP 01

    Choose nonclinical documents

    Use approved operational procedures and synthetic requests with no patient information. Define access rules and questions that require staff help.

  2. STEP 02

    Record versions and owners

    Store procedure IDs, approval dates and source links. Connect services and teams. Retire old versions and refresh text and vector indexes after changes.

  3. STEP 03

    Show the approved source

    Apply access and version filters before retrieving passages. Display the current document and owner. Route missing or conflicting guidance to staff.

  4. STEP 04

    Review with staff

    Test retired documents, ambiguous questions and restricted access. Keep staff review during the pilot and remain within the approved nonclinical scope.

05 / Testing

What to measure

Compare these results with your current process before rollout.

Current-source accuracy

Check how often results point to the active procedure for the requested service and site.

Citation validity

Verify that each answer is supported by the linked document and version.

Access isolation

Test that users cannot retrieve documents outside their authorized scope.

06 / Sources

Examples from the industry

Published projects and reference material relevant to this use case.

Industry example 7 June 2023

Google Cloud & Mayo Clinic

Google Cloud collaborates with Mayo Clinic on generative AI

The organizations announced Mayo Clinic as an early adopter exploring enterprise search to help staff find information and support healthcare and administrative workflows.

Read the source
Industry context HHS guidance

U.S. Department of Health & Human Services

Guidance on HIPAA & Cloud Computing

HHS explains that cloud providers handling electronic protected health information for covered entities or business associates can have HIPAA obligations, including an appropriate business associate agreement.

Read the source

These are industry references, not OriginChainDB customer stories. The implementation above is a proposed example.

Build with OriginChainDB

Discuss your application with us.

Explore use cases Talk to our team