Skip to project
PK® / CareSignal

AI-assisted sales operations / explainable by design

CareSignal / Healthcare lead-scoring system

Turn fit signals into a reasoned review queue.

A source-aware organization-research and 0–100 ICP prioritization product—built with official public registries, explicit unknowns, visible weights, and a human-gated CRM handoff.

  • 100%Inspectable scoring
  • 0Patient / PHI fields
  • HumanFinal review gate
ICP70Qualified threshold
Org fit / 25Scale / 20Need / 25Readiness / 15Intent / 15

Deterministic rules online

Public organization data only

Live research is limited to official public organization registries. No patient data, protected health information (PHI), personal contact enrichment, credentialing decision, or automated outreach is used.

Investment-grade operating lensHealthcare revenue operations
Executive decision

Which healthcare organizations deserve human account review, and why?

Primary KPIQualified-account acceptance rate

Share of surfaced qualified accounts that a human reviewer accepts for the next approved sales step.

Human outcome

Revenue teams can focus scarce research time on inspectable organization-level fit evidence instead of opaque scores or scraped contact lists.

Outcome targets require the organization’s own baseline; the portfolio does not invent performance or ROI.Build the 30-day pilot →

01 / Accessible system workflow

Five bounded stages.
One human decision.

The interface turns a sales-operations process into readable HTML, so the architecture remains understandable without animation, canvas, or an image.

  1. 01

    Resolve the organization

    Search CMS NPPES, CMS Provider Data Catalog, and GLEIF; a person chooses the correct legal entity or location.

  2. 02

    Apply visible ICP weights

    Five deterministic factors contribute a documented maximum of 100 points.

  3. 03

    Explain qualification

    Show every subscore, rationale, and the 70-point human-review threshold.

  4. 04

    Suggest role functions

    Recommend decision-maker roles without identifying or inferring individual people.

  5. 05

    Preview the handoff

    Export facts, unknowns, evidence bases, completeness, and score rationale in a browser-local CRM preview.

Organization fit 25Scale 20Need 25Readiness 15Intent 15

02 / Research + scoring lab

Find the organization.
Audit every assumption.

Search official public registries or use a synthetic fixture. Verified facts, user estimates, unknowns, and scoring inferences stay visibly separate.

Live organization research

Start with a legal name.

Official sources

For US providers, add a state or ZIP to reduce ambiguity. Do not enter a person, patient, email, phone number, or PHI.

Search official public registries, then verify the correct location before applying facts.

Identity resolution

Awaiting search

Verify before use
What gets researched
  • CMS NPPES organization identity and taxonomy
  • CMS hospital registration and public facility facts
  • GLEIF legal-entity identity where an LEI exists

Employee totals are never guessed. These official registries do not provide reliable enterprise-wide employee counts.

Editable organization profileOrganization data only

This browser-local demo has no person, email, phone, patient, diagnosis, claim, or medical-record fields.

Deterministic ICP priority scoreThreshold 70
100/ 100

Qualified for human review

Northstar Community Health — Synthetic

Every point is accounted for below. This prioritization score is not a conversion probability and never triggers outreach.

Evidence completeness100%
Decision confidenceHigh
Official record selectedNo

Northstar synthetic fixture scored.

Organization fit25 / 25

Multi-site health systems match the primary organization profile.

Operating scale20 / 20

3,200 employees (synthetic demo fixture) contribute 12 of 12 points; 35 locations (synthetic demo fixture) contribute 8 of 8 points.

Operational need25 / 25

Patient access is a high-value operational use case for this synthetic ICP.

Technical readiness15 / 15

An integration owner and API pathway reduce implementation uncertainty.

Buying intent15 / 15

A 0–3 month window is a strong near-term intent signal.

Role-based next step

Suggested decision-maker functions

Functions only—no names, profiles, emails, or inferred identities.

  • VP of Patient Access
  • Chief Information Officer
  • Chief Operating Officer
Precision checklist

Core scoring fields are complete

Still verify source dates, scope, decision authority, and whether the stated need is current.

Executive decision

Advance to evidence-led discovery

The 100/100 priority score clears the configured human-review threshold and 100% of required evidence checks are complete. This supports discovery priority—not purchase intent or conversion probability. Strongest scored factor: Organization fit.

Next best action: Have the account owner verify source dates, workflow ownership, decision authority, and a measurable business problem before any outreach.

Evidence boundary: Official registries support organization identity and selected facility facts. Employee count, enterprise location total, operational need, readiness, and buying timing may be user-provided, estimated, or unknown. The advance/verify split reuses CareSignal’s displayed High/Medium/Low evidence-completeness bands; it is a portfolio pilot convention, not a validated optimum. The 0–100 result is a transparent prioritization score—not a clinical judgment, purchasing signal, probability, or authorization to contact anyone.

Shadow-pilot design

Prove prioritization value before changing the sales motion

  1. Run in shadow mode on a consecutive, representative account cohort. Keep current qualification and outreach decisions unchanged while reviewers record agreement, disagreement, evidence gaps, and final dispositions.
  2. Compare score bands with human review outcomes and later verified discovery progression. Report results by organization type, size band, geography, and evidence completeness so one segment cannot hide weak performance in another.
  3. Calibrate or replace the threshold before operational use. Advance only when the organization chooses minimum acceptance and false-positive tolerances from its own baseline, quality is stable across decision-relevant segments, and no account is contacted automatically.
Executive KPI scorecard

Three measures with explicit guardrails

  1. Human review acceptance by score band
    Definition: Accounts accepted for verified discovery ÷ accounts reviewed, reported separately for each score band and evidence-completeness band.
    Decision use: Shows whether the ranking concentrates accounts that reviewers judge worth a discovery conversation; it does not estimate conversion probability.
    Guardrail: Define acceptance before the pilot and audit reasons for disagreement so reviewers cannot raise the metric by silently changing the qualification standard.
  2. False-positive review rate
    Definition: Above-threshold accounts rejected for material fit, evidence, consent, or timing problems ÷ all above-threshold accounts reviewed.
    Decision use: Identifies wasted seller effort and helps determine whether the threshold or factor weights need recalibration.
    Guardrail: Track rejection reasons and segment results; do not optimize away smaller, rural, nonprofit, or less digitally mature organizations without an explicit business justification and fairness review.
  3. Median evidence-to-decision time
    Definition: Median time from a complete organization research packet to a recorded human qualification decision, with the 90th percentile also reported.
    Decision use: Measures whether the workflow reduces research and review delay without substituting an automatic decision for accountable judgment.
    Guardrail: Pause the clock while required evidence is unavailable, and never reward speed that lowers source quality or bypasses privacy, consent, or human approval checks.

03 / Explicit handoff

Preview the CRM payload.
Transmit nothing.

This demonstration maps the evaluated organization into a HubSpot-style company property object. It never authenticates, calls HubSpot, creates a contact, or sends data off the page.

Demo boundary

Human review stays between scoring and outreach.

  1. 01
    Review

    Confirm organization facts and score rationale.

  2. 02
    Approve

    A person decides whether a CRM handoff is appropriate.

  3. 03
    Download

    Export a local JSON preview for discussion or implementation planning.

No external transmission. The download is created in this browser.

HubSpot company handoff / previewLocal only
{
  "object": "companies",
  "mode": "demo_preview_only",
  "properties": {
    "name": "Northstar Community Health — Synthetic",
    "domain": "northstar-health.example",
    "healthcare_organization_type": "Health system",
    "numberofemployees": 3200,
    "employee_count_basis": "Synthetic demo fixture",
    "location_count": 35,
    "location_count_basis": "Synthetic demo fixture",
    "operational_priority": "Patient access operations",
    "technical_readiness": "API-ready systems and integration owner",
    "buying_timeline": "0–3 months",
    "icp_score": 100,
    "qualification_status": "QUALIFIED_FOR_HUMAN_REVIEW",
    "evidence_completeness_percent": 100,
    "decision_confidence": "High",
    "executive_decision": "Advance to evidence-led discovery",
    "next_best_action": "Have the account owner verify source dates, workflow ownership, decision authority, and a measurable business problem before any outreach.",
    "score_version": "deterministic-care-signal-v2",
    "score_rationale": "Organization fit: 25/25 | Operating scale: 20/20 | Operational need: 25/25 | Technical readiness: 15/15 | Buying intent: 15/15",
    "suggested_decision_maker_roles": "VP of Patient Access | Chief Information Officer | Chief Operating Officer"
  },
  "provenance": {
    "selected_official_research_record": null,
    "organization_identity": "Synthetic fixture",
    "employee_count": "Synthetic demo fixture",
    "location_count": "Synthetic demo fixture"
  },
  "privacy": "Organization-level attributes only. No contact records, patient data, or PHI.",
  "governance": {
    "evidence_boundary": "Official registries support organization identity and selected facility facts. Employee count, enterprise location total, operational need, readiness, and buying timing may be user-provided, estimated, or unknown. The advance/verify split reuses CareSignal’s displayed High/Medium/Low evidence-completeness bands; it is a portfolio pilot convention, not a validated optimum. The 0–100 result is a transparent prioritization score—not a clinical judgment, purchasing signal, probability, or authorization to contact anyone.",
    "pilot_mode": "Shadow mode only; no automatic qualification, CRM write, or outreach.",
    "kpis": [
      {
        "name": "Human review acceptance by score band",
        "definition": "Accounts accepted for verified discovery ÷ accounts reviewed, reported separately for each score band and evidence-completeness band.",
        "guardrail": "Define acceptance before the pilot and audit reasons for disagreement so reviewers cannot raise the metric by silently changing the qualification standard."
      },
      {
        "name": "False-positive review rate",
        "definition": "Above-threshold accounts rejected for material fit, evidence, consent, or timing problems ÷ all above-threshold accounts reviewed.",
        "guardrail": "Track rejection reasons and segment results; do not optimize away smaller, rural, nonprofit, or less digitally mature organizations without an explicit business justification and fairness review."
      },
      {
        "name": "Median evidence-to-decision time",
        "definition": "Median time from a complete organization research packet to a recorded human qualification decision, with the 90th percentile also reported.",
        "guardrail": "Pause the clock while required evidence is unavailable, and never reward speed that lowers source quality or bypasses privacy, consent, or human approval checks."
      }
    ]
  },
  "transmission": "None. Browser-local preview and download only."
}

04 / Qualified-leads dashboard

A queue built for review,
not automated pursuit.

Only fixtures at or above 70 appear in the qualified queue. Scores prioritize investigation; they are not evidence that an organization wants contact.

Fixture set6

Invented organizations

Qualified3

Score ≥ 70

Fixture consistency100%

6 of 6 invented cases

Personal / patient fields0

Organization attributes only

Qualified synthetic organizations sorted by ICP score
Synthetic organizationScoreStrongest signalSuggested roleDecision
Northstar Community Health — Synthetic100 / 100Organization fitVP of Patient AccessHuman review
Meridian Specialty Network — Synthetic84 / 100Organization fitVP of Revenue CycleHuman review
BrightPath Digital Health — Synthetic72 / 100Technical readinessVP of PartnershipsHuman review
Fixture evaluation outcome

6 of 6 synthetic fixtures match their predeclared qualified-or-nurture expectation at the 70-point threshold. This measures deterministic rule consistency on a tiny invented fixture set—not predictive accuracy, production lift, or fairness across real organizations.

05 / Source contract

Official evidence in.
Unknown stays unknown.

Each source supports a bounded set of organization facts. None is treated as proof of buying intent, technical readiness, enterprise headcount, or the total number of operating locations.

01

CMS NPPES NPI Registry API

Supports

US organization-provider identity, NPI, taxonomy, registered practice address, record update date.

Does not establish

An NPI does not validate licensure or credentials and does not provide employee totals.

02

CMS Hospital General Information

Supports

Medicare-registered hospital identity, CCN, address, type, ownership, emergency services, and rating when reported.

Does not establish

Facility coverage is not an enterprise roster or an employee-count source.

03

GLEIF LEI Index API

Supports

Legal-entity name, LEI, registered address, entity status, and registration freshness where an LEI exists.

Does not establish

Not every healthcare organization has an LEI; the index does not provide workforce totals.

06 / Product walkthrough

See the scoring decision
from input to handoff.

The 13-second walkthrough moves from the system overview through scoring, handoff, and the qualified-account dashboard. The text sequence beside it provides the same essential narrative.

CareSignal / healthcare lead-scoring walkthrough
Text walkthrough
  1. 00:00

    Read the product boundary and 70-point qualification threshold.

  2. 00:03

    Follow the five-stage scoring and review architecture.

  3. 00:05

    Inspect a 69/100 nurture result and every weighted explanation.

  4. 00:08

    Preview the browser-local, no-transmission CRM handoff.

  5. 00:11

    Review the synthetic qualified-account dashboard and fixture outcome.

07 / Technology

A small stack with
an explicit job for every layer.

No generative model is used in the score. AI-assisted engineering supported product framing, implementation, adversarial review, and evaluation design.

01

React 19

Interactive fixture selection, editable organization inputs, and browser-local state.

02

TypeScript

Typed inputs, scoring factors, qualification results, and CRM-preview structure.

03

Deterministic scoring

Five inspectable weighted rules; no model inference and no hidden coefficients.

04

CSS Modules

Responsive product interface, accessible focus states, and an isolated visual system.

05

Official public APIs

Best-effort organization research through CMS NPPES, CMS Provider Data Catalog, and the GLEIF LEI Index.

06

Node test runner

Source and rendered-route checks for weights, boundaries, semantics, and export behavior.

08 / Safeguards

What this system
refuses to pretend.

Healthcare-adjacent software earns trust by making its exclusions as concrete as its capabilities.

01

Facts keep their source

Live registry fields, synthetic fixtures, user estimates, unknowns, and scoring inferences are labeled separately. Search results require human identity selection.

02

No patient or PHI surface

The interface accepts organization context only. There are no patient, diagnosis, treatment, claim, medical-record, or health-outcome fields.

03

No personal prospecting

The system suggests role functions such as VP of Patient Access. It never supplies names, profiles, emails, phone numbers, or inferred identities.

04

Human-gated qualification

A score above 70 creates a review priority—not permission to contact, evidence of intent, or an automated sales action.

05

Local handoff preview

The HubSpot-style payload is displayed and downloaded in the browser. This demo has no HubSpot credential and performs no external transmission.

06

No fabricated headcount

The official registries used here do not supply reliable enterprise-wide employee totals. CareSignal leaves the field unknown unless a user enters and labels a sourced figure or estimate.

Explainable qualification / human controlled

Score a synthetic lead.

Open scoring lab ↑Route a reviewed lead →Private source review ↗