How to Automate Net Health

Net Health builds for one department at a time

Net Health does not make a general EHR. It makes several specialty ones, each aimed at a department that hospital-wide software tends to serve badly: WoundExpert for wound care, ReDoc and Optima for rehab therapy in outpatient clinics, skilled nursing and senior living, plus hospice, employee health and occupational medicine.

The wound center is the clearest example of why that exists. It is often a hospital outpatient department, sometimes run under contract by a management company, seeing the same patients every week for months. Its record is not a series of separate visits. It is a healing trajectory: this wound, at this size, in this week, on this treatment.

General software records that badly, because it was designed around encounters. WoundExpert is designed around the wound, with photographic documentation and measurement through Tissue Analytics, and benchmarking against the wound database Net Health has assembled across its customers.

Healing is measured weekly and approvals are not

The clinical rhythm of a wound center is weekly. The patient comes in, the dressing comes off, the wound is measured and photographed, and the plan changes based on what the last seven days did.

The administrative rhythm runs on somebody else's clock entirely.

A skin substitute needs prior authorization, and the payer limits how many applications it will cover. Hyperbaric oxygen therapy needs approval, with coverage criteria that have to be documented before the first treatment. The supplies the patient takes home come from a DME supplier with its own portal and its own idea of when the order shipped. Many patients arrive by referral from a hospital discharge, a nursing home or a podiatrist, and those referrals sit in whatever system the referrer uses.

When the approval is late, the visit still happens. The dressing still gets changed. The treatment the wound actually needed just slides a week, and a week is a long time in a wound that is not closing.

Net Health

Approvals ready for the next visit Pending authorizations checked on the payer's own site daily, so a treatment is scheduled rather than postponed a week.

Applications counted before they run out How many covered applications a patient has left, tracked early enough for the conversation to happen in advance.

Supplies followed to the doorstep Orders watched on the supplier's portal until they ship, because a patient without dressings loses the week.

Tissue Analytics measures what the camera can see

Net Health has automated the documentation side hard, and a center running it should not be doing any of that by hand.

Tissue Analytics measures the wound from a photograph, tracking area, volume and healing velocity across visits rather than relying on a ruler and someone's handwriting. Ambient AI documentation captures the conversation between provider and patient and populates the assessment, treatment and procedure notes. CPT codes populate the superbill from what was documented, which matters in a specialty where the coding is fiddly and the money is in the procedures. Offline mode keeps a nurse or therapist working where the network does not reach. Over the top of it sits benchmarking, which shows a center how its healing rates compare with the wider database.

All of that acts on the wound and the visit. The department's own record is thoroughly handled.

A payer's authorization queue is not the department's record. Neither is the supplier's order portal, the referring hospital's discharge system, or the site where a visiting physician's privileges quietly expire. Those hold the facts deciding whether next week's treatment can go ahead, and they open only for a person with a password.

The approval can arrive before the next dressing change

The password is the entire gate, and the clinic already holds it. Going through it every morning is the part that never happens.

Every pending authorization checked on the payer's own portal each morning, so a skin substitute approved on Tuesday goes onto Thursday's visit instead of being discovered the following week. Applications already used counted against the payer's limit, so the conversation about what happens when they run out is had early rather than in the room.

Hyperbaric approvals tracked to a decision, with the ones still pending listed by how long they have sat and which patient is waiting on them. Supply orders followed on the supplier's portal until they actually ship, because a patient without dressings between visits is a wound going backwards. Referrals collected from hospital discharge platforms and referring offices, so nothing waits in a queue over a weekend. Physician credentialing and privilege expiry dates read off the sites holding them.

The line does not move in a clinical department. Gathering and checking runs unattended. Anything that changes a clinical or billing record, submits a request or reaches a patient is prepared for a qualified person to review and send.

A clinic day that starts with the answers already in

The wound care nurse is the one who knows which patients are worrying. Spending the first hour finding out whether a payer has decided anything is not what that knowledge is for.

WebRun is an AI agent that works a real Chrome browser, signed in as your staff are. It opens the payer portal, the supplier's order page or the referral system, reads what is on the screen, and hands back the list before clinic starts: approved, denied, still pending, shipped.

It runs on your schedule in your own private environment, sessions are not shared between tools, and a workflow can be locked to a named list of domains. You can watch a run and stop it, and nothing is written into a patient record.

The workflows below are already built, and each one names what it opens.