Compliant Healing Intelligent Platform

Your note already says it. CHIP shows you what a payer will say back.

CHIP reads the wound-care note your provider wrote — typed, scanned, or photographed — and turns it into the record a payer expects: measurements, healing trajectory, coverage criteria, and the products that match them.

Wound-care practices billing Medicare · nothing leaves your server

CHIP reading Wound #1 · sacrum
“Sacral wound measures 8.3 x 6.1 x 1.3 cm, 88% granulation, heavy serosanguineous drainage. Stage 4. Undermining present at 3 o'clock.”
Measurements8.3 × 6.1 × 1.3 cmread
ThicknessFull thicknessfrom stage 4
ExudateHeavyread
Trajectory−10.5% over 7 days2 visits
PerfusionNot documentedgap
Perfusion is not in this note. CHIP will not assume it. The gap is surfaced now, while the patient is still in the room.
How it works

Upload the note. Confirm the plan. Place the order.

No new charting system, no second place to type. CHIP works from the documentation your providers already produce.

01

It reads the note

PDF, scan, or a phone photo of a printed chart. Text extraction first, on-device OCR when the page is an image. Multiple visits of one patient merge into a single healing timeline.

02

It checks the criteria

Every finding is matched against the coverage rules that govern it, with the LCD or article named. What the note supports is marked. What it doesn't is flagged, not filled in.

03

You sign and order

Confirm the dressing or graft, and CHIP writes the clinical note for signature and carries the plan into a referral, HealKit, or NPWT order — quantities already calculated.

The rule CHIP will not break
If the note doesn't document it, CHIP says it isn't documented.

An undocumented depth is not zero. An unrecorded wound bed is not clean. A venous ulcer is not assumed painful because venous ulcers usually are.

Software that quietly fills a gap produces a record that reads well and cannot be defended. CHIP does the opposite: it shows you the gap while it can still be closed, and where a finding is true but rarely written down, it asks the provider to attest it — stored separately, so an auditor can tell what was read from what a clinician asserted.

Coverage

The rules it checks, by name

Not "AI-powered compliance." Specific policies, cited on the page, so your team can check CHIP's reasoning instead of trusting it.

LCD L33831Surgical dressingsPrimary and secondary selection by thickness and exudate, with the covered change frequency and the per-code allowance.
LCD L33821 · PA A52511Negative pressure wound therapyQualifying wound type, the programme that must have failed first, and the four conditions that exclude coverage.
Article A56175Non-contact ultrasound (97610)All eight qualifying criteria, and the codes it cannot share a date of service with.
NCD 270.3Platelet-rich plasma (G0465)Diabetic indication, the 20-week limit, and the wound-bed condition that has to hold before it applies.
Security

Patient data does not leave your server

Extraction, coverage checking and the clinical language model all run inside your own environment. That is an architectural property, not a policy promise — there is no outbound call to switch off.

01On-server extractionNotes are parsed and OCR'd in place. Nothing is sent to a third-party service to be read.
02Local clinical modelThe language model is installed with the platform and runs beside it. It makes no outbound requests.
03Opt-in cloud features, killableThe few features that do use an outside service are per-account, BAA-covered, and can be disabled platform-wide with one switch.
04Stored files are not web-readableUploaded records are served only to an authenticated session — never by direct link.

See it read one of your own notes

Bring a real chart — the messier the better. The most useful demo is the one where CHIP finds something your last denial was about.