Let's talk →

Release notes

Straight from
the workshop.

We ship constantly and tell you about it in plain language. Last updated November 2, 2026.

  1. Vigil Rolling out Services · Home page: billing action items · Billing records

    Services

    • Billing staff can now enter services. The service screen no longer opens read-only for them.
    • Billing staff can also correct a completed service (Vigil asks for a reason and keeps a record of the change). They still cannot delete a service.

    Home page: billing action items

    • Each urgent billing line in "Your Action Items" now says what is wrong, for example "Billing: Missing Subscriber Insurance ID".
    • When you fix the cause — a service template, a staff member's NPI, a client's diagnosis, a billing record, client demographics or payer setup — Vigil re-checks the affected bills for you.
    • The home page re-checks its billing lines each time it opens, so an item that is already fixed leaves the list on its own.
    • A bill that billing staff sent back to you stays on your list until you deal with it.

    Billing records

    • Existing billing records ask for the ID the next time they are opened.
  2. Vellum Released A personal home page · Report cards show what changed · "How this report works" in your downloads · Profile pictures · A softer look

    A personal home page

    • The home page now greets you by name and is built around your organization.
    • An Achievement Spotlight celebrates real wins: a report figure reaching its best reading or a run of improvements, a reporting deadline met on time, a support request resolved. It only appears when the data behind it is up to date, so a stalled import is never mistaken for progress.
    • "Worth a look" lists anything that needs your attention, plus a couple of pages you haven't tried yet.
    • A Support card shows your open requests and your organization's upcoming reporting deadlines.
    • What's New lists the latest Vellum updates, like this one, with a dot on any you haven't read yet. Your organization's Data Freshness card sits beside it.

    Report cards show what changed

    • The stat cards on every organization's reports now show how much each figure moved since the last day the report was run, for example "up 4.2% vs Oct 22".
    • Green means it moved the good way and red the other way. Days nobody ran the report are skipped, and the badge always names the date it is comparing to.

    "How this report works" in your downloads

    • Excel downloads now include a "How this report works" sheet with the same explanation as the report's on-screen panel, so a workbook still explains itself after it is shared.

    Profile pictures

    • Everyone starts with a random pick. Change it, or go back to your initials, from My Profile.

    A softer look

    • Colours across Vellum are softer and consistent. Pages, charts, Excel downloads and emails now share one palette. Green still means good, amber needs attention and red is a problem.
  3. Vigil Rolling out ABA Services: a watch becomes a service · Service templates: who may deliver it, and at what rate · Clients: prior authorizations · Claims billing · Service Entry and a client's services · Billing setup · …

    ABA Services: a watch becomes a service

    • Each ABA service template has an "ABA session type" (Direct treatment, Protocol modification, Caregiver guidance, Assessment, Group treatment). A watch begun in the Spyglass takes its template from the session type, the client's program and the staff member signed in. The "Billable / Non-billable" choice is gone.
    • When the RBT signs the watch, with a short session note, it becomes a service and bills through the same rules as every other service. Units come from the watch's active time, rounded by the template's Rounding rule.
    • A watch that cannot become a service yet keeps all its data and says why. A second observer can join from the Begin sheet and is never billed. One staff member cannot bill two watches that overlap in time.
    • A protocol modification during direct treatment is billed by default; a funding source can be set to "Does not pay this service while another ABA service runs", and such claims get their own Needs attention group with Move and Remove bill.
    • A watch that ended while offline can now be signed.
    • Behavior targets now come only from treatment plan objectives, one per objective, on blueprints with "Behavior tracking (ABA)" turned on.

    Service templates: who may deliver it, and at what rate

    • New "By Provider Type" tab on every template: a provider type (optionally for one funding source) with its own procedure code, up to four modifiers, or rate. The most specific rule wins, field by field. Once a template has rows, only those provider types may deliver it. Services already saved keep their price.
    • New Rounding rule: Round up, Midpoint (more than half), or Whole units only.
    • A funding source can carry its own unit length, and its own "Prior authorization" setting (the single box on the template is gone).

    Clients: prior authorizations

    • A client's Coverage lists their authorizations when a payer needs one: number, payer, service, units and dates. A claim with no covering authorization, or with none left, waits in Billing with the reason. The number goes on the claim.

    Claims billing

    • Test or Live for each clearinghouse: a Test file is checked but no payer is asked to pay; every batch remembers what it was built as; a Test batch never marks a claim as sent, and only a Live batch can be recorded as answered or paid.
    • Eligibility checks through the Availity API take Test or Live from the connection that holds its sign-in; answers to a Test check are never saved.
    • Who is named on the claim when the clinician cannot be: hold, the QP supervisor, the supervisor whenever the clinician is not marked licensed, or the agency's NPI only. The same choice can be given to every payer on a routing at once.
    • Needs attention: a "Problem" filter with counts, "Show next" / "Show all" on long groups, and Remove bill for several ticked bills at once, with each one that stayed and why. Each removable bill says why it should not exist.

    Service Entry and a client's services

    • On a new service, the Billing and FASAMS cards show what the service will be stamped with when saved. A template procedure code missing from your list is said before you save.
    • The client's Services list has a Staff filter, and both it and Service Search have "FY" and "All" date buttons.

    Billing setup

    • Add payer and Add category show again. Administrators whose Access template allows changes to Configuration see the payer toolbar, payer card and Export. From a client's page, Configuration and Billing setup open in a new tab.

    Reports Workshop

    • People has the diagnosis fields (one row per person unless "One row per diagnosis" is on); diagnosis lists show code and description, sorted by code; a Yes/No column can be one per diagnosis code.
    • "Add a filter" opens on a new row instead of replacing a filter you already set.

    Audit log (administrators)

    • New in Configuration: who opened, changed and exported what, and when, with search; a Usage view of screens opened and people active by week; and a dashboard of activity over time, top screens, when people use Vigil, and browsers and devices.

    Staff, Lookup tables and FASAMS

    • "Provider Type" is now "Billing provider type"; RBT, BCaBA and BCBA are built in. Certifications 1 to 3 are back and saved again (billing does not read them).
    • Lookup tables: after you add a value, the form clears and the new value lights up in the list.
    • The "Ordering County" question on the FASAMS legal forms now lists counties.

    Lanterns

    • "Welcome to Vigil" (Welcome to Vigil, A client's record) for everyone. The Lanterns page is grouped by chair: Welcome, Clinician, Billing desk, Configuration. "First weeks" now starts with "Your day on Home".
    • "Billing and data": Add a service for billing, Read the Billing card, When Add Service stops you.
    • "Setting up Vigil" is complete at 12 (Treatment plans, Opening day); "Setting up FASAMS" adds "A template for every step".
    • Four ABA paths: Setting up ABA (7), ABA in your day's work (6), Supervising ABA (6), How an ABA session becomes a claim (3).
    • Each lantern lit now pays Sparks (a whole path with its honor pays up to 75); lanterns lit earlier are paid once.

    Glimmers

    • The Team Wall: faces with their ring, the honor, its rarity and how much of the grove holds it; "Everything" or "Rare and above"; "Show more"; and a card per colleague (their Kindled, when they joined, their rarest honors on the wall), never a level, Sparks or count. Only some honors appear on it; clinical, sign-in and attendance, volume and client-photo honors stay private. Only honors earned as they happened, from staff who have not turned Glimmers off. It turns on with the database update; until then it says it is being readied.
    • The Little Cauldron is now the Bubbling Cauldron. A tap on the Trick-or-Treat Pail throws a shower of sparks.
    • The top bar and sign-in page dress up for Valentine's Day, St. Patrick's Day, Easter, Thanksgiving and Christmas. Vigil has its own browser-tab icon.
  4. Vigil Rolling out Later, when you turn on the treatment plan check · Treatment plans: each plan event is a session you record · Treatment plans: signing · Treatment plans: deadlines and your Home page · Treatment plans: setting them up · Treatment plans: the plan check on claims (optional) · …

    Later, when you turn on the treatment plan check

    • The check on claims is off when the update is installed. Nothing about billing changes until you choose a start date.
    • First, on Service templates, tick "No treatment plan needed" on every service done before or without a plan: intake, screening, assessment, crisis and mobile contacts, and group or bed-day services whose attendees may have no episode.
    • Then set the start date on the Treatment plan blueprints page. Vigil first shows how many open bills the check would hold; read that count before you save. The check applies to admissions from that date on.
    • For clients already in care whose plan was written elsewhere, record it on the episode with "A plan was written outside Vigil...", with its scanned copy, so their sessions are covered until their next review.

    Treatment plans: each plan event is a session you record

    • Writing the first plan, each review, an amendment and the discharge plan are now ordinary services: you enter the date of service and the start and end time, then everyone the plan needs signs it.
    • Start from the episode (Create Plan, Review Plan, Amend plan..., Record the discharge), or from Add Service, which lists each plan service once ("Treatment Plan - Initial", "Review", "Amendment", "Discharge") and opens the plan.
    • Before a plan can be signed, Vigil lists what must be on file: the client's date of birth, an active diagnosis on the episode, and a legal guardian for a client under 18. Each one says where to fix it.
    • Each goal needs at least one measurable objective, and each intervention says who provides it and how often. "Did the client take part in writing this plan?" starts on "Choose..." and must be answered.
    • A plan is effective the day the last signature comes in, and the next review is counted from that day. An amendment does not move the review date.
    • A plan session is billed only once everyone it needs has signed, through the same rules as every other service. A discharge plan recorded with the client not present is never billed.
    • To fix the date or time of a plan session nobody has signed yet, choose "Change the date or time" and give a reason. After someone has signed, void the signatures first. Every change is recorded.
    • When a signed plan is corrected and signed again with nothing changed in what it says or who signed it, it keeps its original effective date. If the content or the signers changed, it takes the new date.

    Treatment plans: signing

    • One card for each signature the plan needs: the clinician, the client (or the guardian, for a client under 18 or with a legal guardian on file), and the supervisor when the clinician is not licensed or the blueprint asks for one.
    • If the client will not or cannot sign, choose Declined, Unable right now, or (at discharge) Not present, and say why. On a first plan or an amendment, a refusal is confirmed by the supervisor. A plan waiting on an "unable right now" stays unbilled until the client signs, or the supervisor records it as final.
    • A supervisor not ready to sign can "Return with a note". The clinician sees the note on their Home page and on the plan.
    • Saving a change to a plan sets aside the signatures already given, so everyone signs what changed. If the plan changed while you had the signing screen open, Vigil asks you to look again before signing.
    • "Finish later" keeps everything; the episode and each person's Home page say who it is waiting for.
    • A printed plan that is not yet signed is marked "DRAFT — not signed, not in effect". The printout shows the date of service, the effective date, and any refusal with its reason.

    Treatment plans: deadlines and your Home page

    • The episode shows where each plan stands (Draft, Awaiting signatures, Active, Review due, Overdue, Closed) with its deadline and who it is waiting for, and one main next step.
    • After a client is discharged, review deadlines stop and the episode shows "Discharge plan due".
    • Your Home page lists plans waiting for your signature, your plans waiting on someone else (with any returned note), and plan deadlines coming due, most urgent first.
    • A plan keeps the deadlines it was written under. Changing a blueprint's days later affects only plans and reviews that come after.
    • Billing staff can see why a completed plan session did not bill.
    • On a service, the "Objectives addressed" card is now saved with the service, so it follows the service's signatures and its record of changes. If the objectives cannot be loaded, it says so instead of showing empty boxes.

    Treatment plans: setting them up

    • Treatment plan blueprints now has its own page like Sites and Service templates: the list beside the form, Save in the header, and Keep editing / Discard when you leave with changes. Configuration > Treatment plans opens it; the old treatment plan configuration page takes you there.
    • Each blueprint holds its programs, when the first plan is due, the template for each plan event, who signs each event, and what the plan includes. A program belongs to one blueprint.
    • Make the default, Duplicate and Delete are on each blueprint. The default, and a blueprint a plan still uses, cannot be deleted. Every change is recorded in words.
    • The "due soon" lead time for plan deadlines is set on the same page, under "For every blueprint".
    • On Service templates, a treatment plan service chooses its "Treatment Plan Event". Who signs it is then shown from the blueprints, not set on the template. Such a template counts in minutes or per encounter, and cannot also carry a FASAMS role.
    • The Golden Thread score is no longer shown in the treatment plan window.

    Treatment plans: the plan check on claims (optional)

    • Once your agency sets a start date, a service entered in Vigil after the first plan's due date is billed only if a signed plan was in effect on its date of service. A plan signed later, or a late review, does not cover the earlier days.
    • The service shows a warning when saved. It can still be signed and still reports to the state; only its claim waits, in Needs attention with the reason.
    • A service that needs a plan but is not on an episode waits too, with a note to put it on the client's episode.
    • A plan written outside Vigil covers the sessions in its window while its scanned copy is on file. Remove it if it was entered by mistake.
    • A bill that is waiting for a plan and was never sent can be removed from Needs attention > Remove bill, one at a time, after you confirm it. Bills from the old plan screens that were never signed by the clinician and never sent are listed there too.
    • A new "Paid, no plan" list in Needs attention shows bills a payer paid for a date with no plan in effect. Vigil never voids or refunds them. Once you have settled one with the payer, press "Settled..." and record whether the payer kept the payment, you refunded it, or the payer recouped it. This records what happened; it does not change the money.

    Billing setup: timely filing limit

    • Each payer can carry a "Timely filing limit": the number of days after the date of service it accepts a claim. Leave it empty if you do not know it.
    • In the last 30 days, Needs attention says "N days left to file with" the payer, or "Past" its filing limit. For a claim to a second payer, the days count from the first payer's answer.

    Signatures and PINs

    • A clinician's or supervisor's signature is always given by the person signed in, or by the staff member whose PIN is entered, with their name and credentials from their staff record.
    • A supervisor signing on someone else's screen enters their own PIN, or signs later from their own sign-in.
    • Signing PINs are 4 to 8 digits and stored more securely. After 5 wrong tries the PIN is locked for 15 minutes. Setting up a PIN now works, and setting it again replaces the old one.
    • Sending a plan to a client or guardian to sign from a link is not available for now. It returns once Vigil can check the signer's date of birth and send a one-time code to contact details already on file.
    • A group session is signed by its own clinician. A group whose service template needs a supervisor's or client's signature cannot be signed as a group, and Vigil says why.
    • A service whose time was not recorded is no longer given a made-up 60 minutes.

    FASAMS

    • When a service entered in Vigil is removed (for example a plan session cancelled to correct its date), the FASAMS file sends the state a delete for it whenever its payer reports to FASAMS, the same way as for services removed in the KIS desktop system.
    • The Drawdown page (The Lamplighter) is now called FASAMS funding. Its door is on the Reports page, for billing administrators, and it is available only when FASAMS is turned on.
    • A blank agency Tax ID now tells you to enter it in Billing setup (Organization, Billing Provider Identity).
    • A service whose site has no site code or no county now says plainly that it is held out of the FASAMS file until it has one.
    • The FASAMS Export Center's messages now point to the Validation tab, and count episodes, not admissions.
    • On Programs, the count of programs reporting under each state placement type now updates as soon as you save.

    ABA Services

    • ABA Services is now listed in Configuration's compliance modules, switched off. Turning it on adds the Behavior Data tab, the Spyglass, behavior targets on treatment plan objectives, and ABA Outcomes on Reports.
    • If the ABA data tables are not installed yet, turning it on says so instead of switching on screens that cannot work.
    • Before you turn it off, Vigil tells you about any Spyglass watches still running or not yet saved as a service. Nothing is lost: they wait, and send once ABA Services is back on.
    • The Behavior Data tab has the same section header as the rest of the client page.
    • ABA Outcomes is now a Quick Pulls card on Reports. It opens on the last six months, and client names open in a new tab.
    • Buttons on the Behavior Data tab and ABA Outcomes now show that they are working, and a message from Vigil is shown in its own words.

    Sites

    • Sites now works like the other setup pages: Add site, Cancel and Save sit in the page header, Save says what you changed, and leaving with unsaved changes asks you to Keep editing or Discard.
    • Each site's site code is now on the page. It is required and must be unique, because it is the site ID the state receives. Changing it warns you first: the state sees the new code from then on, and saved reports that filter on the old code stop matching.
    • A site has one address, the one used on claims, with an address lookup that checks the ZIP+4.
    • The list shows each site's code, city and phone, with "Hidden" and "No county" tags. Hidden sites show when you tick "Show hidden sites".
    • Sites are no longer deleted. Hide a site to retire it; its history keeps its name.
    • Fields nothing used were taken off the page, including the empty physical address, the director fields, and site NPI and taxonomy. Nothing stored in them was deleted.
    • The County and Subcontract section is now labelled FASAMS. When an admission has no subcontract, Vigil's check names the admission's site and why: the site has none, or its subcontract has no line for that year.

    One look across Vigil

    • On Sites, Programs, Staff, Billing setup and Treatment plan blueprints, the list beside a long form now stays in place while you scroll the form.

    Lanterns: three FASAMS training paths

    • "Setting up FASAMS" (administrators, 8 lessons): turning FASAMS on, subcontracts, sites, programs, payers, service templates for the state, the FASAMS forms, and getting ready to report.
    • "FASAMS reporting" (billing and compliance, 4 lessons): the FASAMS Export Center, Vigil's FASAMS checks, after the upload, and FASAMS funding. The built-in Billing template gets this path.
    • "FASAMS in your day's work" (clinicians, 3 lessons): what an admission needs, what comes due again, and discharge.
    • The paths appear only at agencies where FASAMS is available. The "Reporting to the state" lesson moved from the Billing setup path to "Setting up FASAMS" (as "Payers"), and anyone who lit it keeps it lit.

    Glimmers: new honors

    • "Charting the Way": honors for signing treatment plan events, co-signing them as a supervisor, and "The Mapmaker" for setting up or improving a treatment plan blueprint. A signing honor never appears on the signing screen (the client may be there); it greets you on your next page.
    • "Lantern Paths": an honor for finishing every lesson on a Lanterns path, one for each path.
  5. Vigil Rolling out Forms designer: safe to change forms that are in use · Forms designer: a new way to build forms · Forms look the same everywhere · Form settings that now work · Service entry · Lanterns: in-app training for everyone · …

    Forms designer: safe to change forms that are in use

    • A form locks only once a service is saved on it (not as a draft) or signed. Opening it or saving a draft does not lock it.
    • On a form that is in use you can still fix wording and help text, add new questions and choices, retire ones you no longer want, and set an End date. Bigger changes, such as changing a question's kind or what a choice means, are made on a new version, and the designer tells you so in plain words.
    • Saved answers are never lost. A choice someone already picked is retired, never deleted, and a retired question or choice still shows and prints on the services that answered it.
    • Every change to a form is recorded: what it was, what it became, who changed it and when.
    • A wording fix also shows on services already saved on that form, because every service reads its questions from the form. That is why every change is recorded.

    Forms designer: a new way to build forms

    • Editing a question, card, section or care rule now happens in one panel beside the form, and Save at the top names what you are saving ("Save question", "Save form").
    • Quick add under every card: type a question and press Enter, or paste several lines to add several questions at once.
    • Duplicate a question, a card or a whole section.
    • Paste a list of choices instead of typing them one by one.
    • Retire a question with Undo, reorder with the keyboard (Alt+Up and Alt+Down), and share a link straight to a form or a question.
    • While you edit a question, a "How it looks to a clinician" view shows it exactly as it will appear.
    • If two people edit the same item at once, the second save is stopped and told why, instead of overwriting the first.
    • Every signature line now says who signs it: clinician, supervisor, client or guardian.
    • Each question shows its kind of answer in plain words, such as "Text Area".
    • The form list counts correctly ("1 section", "1 service").
    • On narrower screens the editing panel stays beside the form instead of dropping below it.
    • In Configuration, the Form packs row now reads "The forms clinicians fill in on a service."

    Forms look the same everywhere

    • The form preview and the designer now draw a form with exactly the same code clinicians use when entering a service, so what you see while designing is what clinicians get.

    Form settings that now work

    • Minimum and maximum answer length on text questions: a counter shows while typing. An answer that is too long cannot be saved, and one that is too short cannot be signed. Answers saved before a limit was set are left as they are.
    • A form's End date now keeps it out of the form list on service templates. Templates already using it keep it.
    • The form's Effective date field is gone, as it never did anything.

    Service entry

    • Carry-forward now brings choice answers along from the last service, not just typed answers.

    Lanterns: in-app training for everyone

    • Lanterns, Vigil's step-by-step training, is no longer limited to a small group of testers. It has its own Lanterns tab in The Gloaming.
    • You choose who sees which training on the Access page: each Access template has a "Lanterns they can walk" setting. Administrators see every training path.
    • Each training path shows as a card with its keepsake picture and how far you have come (for example "5 of 10 lit"). Open a path to see its lessons as lanterns along a painted trail.

    New training for administrators: "Setting up Vigil"

    • Ten short lessons walk a new site's setup in order: a welcome, Sites, Access, Email, Staff, Billing setup at a glance, Programs, Form packs, Service templates and Lookup tables.
    • The Form packs lesson opens a practice copy of the Forms designer. You find Form packs in Configuration, start and name a new form, see how a form is built (sections are tabs, cards group questions), add a section, a card and a first question, and mark it Required: a draft can still be saved, but the service cannot be signed until the question is answered. It also shows what you can still change once a form is in use, and lets you preview the form the way a clinician sees it.
    • The Lookup tables lesson opens a practice copy of Lookup tables. You search for a list instead of scrolling, tell the values that come built in with Vigil from your agency's own, hide a value your agency does not use, and add your own. A hidden value is not offered again, but records that already use it keep it; nothing is ever deleted, and a hide stays in place through every Vigil update. Some lists, such as payment categories and programs, are changed on their own pages, and the lesson shows you where.
    • The practice screens in the lessons save nothing, so you can try everything safely.

    Lookup tables

    • Values that come with Vigil are now marked "Built in" (they were marked "State list"). They come with Vigil at every agency.

    The Gloaming (was Glimmers)

    • The Glimmers area is now called The Gloaming, with a new icon in the My Account menu. My Glimmers still holds your honors.
    • The top of the page shows a painting of the grove that moves to a different part of it on each tab.
    • It now works like the rest of Vigil: the header and its tabs stay with you as you scroll, and the browser's Back button moves between tabs.
    • My Account no longer shows the Staff link row. Linking a sign-in to a staff member is done on the Access page.

    Setup pages

    • Sites, Staff, Programs, Service templates, Billing setup and Email have clearer, plain headings.
    • Programs hides the FASAMS fields when your agency does not use FASAMS, and Sites only warns about a missing county when it does.
    • On a new site, Service templates now says "No services yet. Press Add Service to start the first one."
  6. Vellum Released Clinical outcomes: Suicide Risk and Safety Follow-Up · Clinical outcomes: Functional Outcomes (FARS / CFARS) · Reports page · Compliance reports and dashboards · Data Import · Services by Subcontract: time rounding · …

    Clinical outcomes: Suicide Risk and Safety Follow-Up

    • A new report shows everyone with a positive suicide-risk screening, from the adult and child C-SSRS forms or PHQ-9 / PHQ-A question 9, and whether they then received a safety plan and follow-up.
    • A ranked worklist puts the most urgent first: anyone discharged after a positive screen, then High risk, outreach and Moderate risk.
    • Each person is routed to a responsible clinician and supervisor. Monthly charts and a by-program view show the trend.
    • The client lists in the workbook are available to administrators only. Small counts are hidden to protect privacy.

    Clinical outcomes: Functional Outcomes (FARS / CFARS)

    • A new report compares each client's admission FARS or CFARS with their latest evaluation in the following 18 months, in any program. So a client admitted through Access and Screening and followed up by another program still counts.
    • Improvement counts only when the score changes by a meaningful amount: 15 points on FARS, 14 on CFARS.
    • The follow-up completion rate is shown beside every improvement rate. Results are split by whether the same clinician or a different one did both evaluations.
    • Views by program, by domain and by admission quarter. Two worklists: active clients who are measurably worse, and evaluations that are overdue.

    Reports page

    • Each report now opens on its own page, with a Back button, a description, the date range and a Run button.
    • The Quick Pulls and My Reports tabs are gone. The report cards are the page, and old bookmarks still land there.

    Compliance reports and dashboards

    • Compliance reports can now be emailed on a schedule (weekly, every two weeks or monthly), one report per program group.
    • "Multi-Program (All Programs)" is now called All Programs Compliance.
    • Med Management now shows compliance by program area in the summary and in the Excel export.
    • Discharge figures now use FASAMS discharge status.
    • The Multi-Program dashboard has been laid out as cards, with better overdue and most-recent filters.
    • All dashboards now share the same card layout. Each card can be expanded to full screen and exported.
    • A new page lets administrators manage who receives the Behavioral Health Data Points email.

    Data Import

    • Each Credible dataset row shows its export number again, so you can tell the reports apart at a glance.

    Services by Subcontract: time rounding

    • Session minutes are rounded to 15-minute units, and every row that changed is flagged "Rounded" with the minutes as recorded, so staff can see it coming and correct notes at the source.
    • Prescriber visits always round down. Other services round down unless they are within 2 minutes of the next quarter hour. Sessions under 15 minutes are left as recorded and flagged.
    • The FASAMS submission now sends the same rounded minutes the review shows, so the two always agree.

    Security

    • Changes to a user's access now take effect straight away. A user who is locked out, loses administrator rights or moves to another organization loses their old access within two minutes, and can no longer download files immediately.
  7. Vigil Rolling out Claims billing: a calmer, clearer page · Claims billing: safer claims · Claims billing: bill details · Claims billing: place of service · Claims billing: sent batches · Eligibility checks · …

    Claims billing: a calmer, clearer page

    • The 837 claims page is now called "Claims billing", and billing has its own teal colour.
    • The count cards at the top are now the tabs: click a card to open its list. The section shortcuts stay at the top as you scroll.
    • Service dates sit inside each list's Filters card, so it is clear which list they narrow.
    • Colours are calmer, and each has one job: the page header shows where you are, a tag shows a claim's state, and red means a problem.
    • A Live or Test tag in the header always shows whether claims are going to the payer for real.
    • Needs attention is grouped by what to do next: may already be at the payer, fix the record, set up the payer, no bill needed, and sent, waiting for an answer.

    Claims billing: safer claims

    • Ready to bill now lists only bills that can go out today. Everything else is in Needs attention, with the reason in words.
    • A bill can no longer go out to a payer other than the one on the client's billing record, twice for the same service, or for a date the client had no coverage.
    • A claim names only someone who may be named: the clinician with their own NPI, or, where the payer allows it in Billing setup, an active, licensed supervisor (their name, NPI and taxonomy together).
    • A claim that may already be at the payer is never sent again on its own. It waits until someone says what the payer has, for example that it never arrived, that it needs a corrected claim, or that the payer already has it. A corrected claim is sent only when someone chooses that answer.
    • Voiding a built batch asks whether the file already went out, and a sent batch the payer has answered can no longer be voided.

    Claims billing: bill details

    • Each problem on a bill has a Fix button that opens the exact place to correct it: the client record, the staff member's NPI, the diagnosis, the billing record, or Billing setup.
    • Client, staff and service names open in a new tab.

    Claims billing: place of service

    • Services entered in Vigil now send the CMS place of service set on their service template. A program can set its own, which is used instead. The template's place of service list now offers the CMS places of service.
    • Telehealth is its own service template, set to the telehealth place of service, so nobody has to choose it per visit.
    • Services entered in the classic KIS program keep their place of service as before.

    Claims billing: sent batches

    • New "Record the answer" on a sent batch, for clearinghouses such as ODMS that send no reply Vigil can read: accepted, rejected, or some claims rejected, with the date and a note.
    • New payer setting in Billing setup, "Accepted means paid": accepted claims for that payer are recorded as paid in full on the date of the answer.
    • A clearinghouse receipt now marks a built batch as sent, and a rejected claim comes back to Needs attention with the reason. A new "Sent, waiting for an answer" list shows what is still out.

    Eligibility checks

    • You can now filter an eligibility batch by client.
    • A batch stays open as you build and send it.

    A bigger Kindled

    • The Kindled in the bottom-right corner is now about a third bigger, so it is easier to see. You can still tuck it away to a small glowing dot at any time.

    Someone else's change is never overwritten

    • If a client's Demographics changed after you opened them (for example a colleague saved a new phone number), your save is stopped instead of quietly putting the older details back. Your edits stay on screen; press Cancel to load the latest, then make your change again.
    • A saved service keeps the answers it was saved with, even when the client record has changed since. A gold mark shows where the client record now says something different.
    • Saving an edited service now updates the client record only with answers you actually changed on that service.
    • Phone numbers typed with an extension or words are kept as typed.

    Glimmers: Halloween in the Bower

    • New for October: a Dragon Suit, and a Vampire Cape worn on your Kindled's back (a new place to wear things).
    • More new pieces: a Trailing Pothos, a Big Leafy Fern, a Favourite Pencil, a Little Watering Can, and a rare Starlight Wand that twinkles from its tip.
    • A new backdrop for the nook: the Mossy Hollow.
    • Every Kindled can now wear the Ghost Sheet.

    Glimmers: gifts and Trick or Treat!

    • An honor can now come with a gift: a Bower piece given free when the honor is earned. Gifts are never sold, and only the people who earned them see them in the Bower. The first is below.
    • Signing in between October 30 and November 2 earns a one-time honor, "Trick or Treat!", and its gift: a little Trick-or-Treat Pail woven from autumn leaves.
    • A gift for someone who has not met their Kindled yet is kept safe until they do.
    • On the day you earn it, your Kindled slips out of its corner, peeks back in, and waits with its new pail. Tap it to open your gift, then let your Kindled carry it or put it in the Bower.

    Glimmers: meeting your Kindled

    • Meeting your Kindled is now a full welcome. The page dims, light rises out of your own work into a glowing grove, and four Kindled wake one by one as you move toward them. The one that recognizes you comes closer and tells you its name (keep it, or give it your own). Then it wakes, and walks with you to its corner as the page lights back up.
    • The welcome has soft sound: a small signature for each Kindled and warm strings as you arrive. A button on the screen turns it off, and it follows your Glimmers sound setting. If your computer is set to reduce motion, the welcome stays still and says each moment in words.
    • Each Kindled now has a birthplace in the Gloaming: the Canopy, the Hearth Hollows, the Still Water or the Standing Stones. Its nook at the Hearth opens there until you choose a backdrop.
    • Each Kindled also brings a small piece from home, a gift that comes with a new honor for meeting it. Staff who already have a Kindled receive theirs the next time they visit the Hearth.
    • A gift that is waiting for you is now shown in your Kindled's paw on your next Hearth visit, with "Keep it on" or "Put it in the Bower".
    • Kindled names follow one rule everywhere: up to 30 characters, using letters (accented letters too), numbers, spaces, hyphens and apostrophes. Names already chosen are kept.
    • Glimmers is now on for everyone. Staff who had it off will see it again, starting with an invitation to meet their Kindled. Anyone can turn it off for themselves at any time on My Glimmers, and it stays off.
  8. Vigil Rolling out Staff page: easier to read and change · Staff page: values that now stay put · Staff page: new and renamed fields · One email for each staff member · Staff photos · Sign-ins and access · …

    Staff page: easier to read and change

    • A staff record now opens as a clean read view. Press Edit to change it; Edit, Cancel and Save sit in the header at the top of the page.
    • Save waits until you change something, and says what you changed (for example "1 change: Title").
    • Switching to another person, or leaving the page, with unsaved changes asks you to Keep editing or Discard.
    • The record has two simple tabs: Profile (name, title, email, home site, supervisor, provider type, employment and work hours) and Credentials & billing (NPI, taxonomy, supervisor for claims, Medicaid PIN, license, education).
    • Old fields nobody used were taken off the screen, including the Payer IDs tab. Nothing stored in them was deleted.
    • The record number, date added and date last changed are in a small "i" beside the person's name.
    • New people added with Add staff appear in the list right away.

    Staff page: values that now stay put

    • Provider type, licenses, academic degree and education level now show their real values, and keep them when the record is saved. Before, saving a staff record in Vigil could clear them.
    • Education level is the one sent to the state on the FASAMS file, so it is worth a quick check on each staff record.
    • A supervisor who has since left now stays on a staff record when it is saved, instead of disappearing.

    Staff page: new and renamed fields

    • New: a Licensed switch, so you can mark who is licensed (Reports can already filter on it).
    • New: each person's work hours. Scheduling uses them to show when someone is available.
    • "Insurance Credential ID" is now called "Credentials after name". It is what prints beside a staff member's signature (for example LCSW).
    • The "Other payer PINs" card has been removed. Numbers already stored there are kept.

    One email for each staff member

    • The email on a staff record's Profile tab is now also the email their sign-in uses for password keys and notices. Changing it in one place changes it for both.
    • If the Profile email is blank, Vigil shows the sign-in's email, so saving never removes where password keys go.
    • The Access tab shows the sign-in email and tells you if it differs from the Profile one.
    • After you update, it is worth checking that each staff member's Profile email is the one they actually use.

    Staff photos

    • Each person now adds their own photo from their own profile. Administrators can remove a photo but no longer add one for someone else.
    • Photos added by an administrator before this update still show.
    • Staff photos now show on the caseload card on a client's page.
    • The honor for adding photos for your team can no longer be earned. Anyone who already has it keeps it.

    Sign-ins and access

    • The old Crew Management page is retired. Sign-ins and access are managed on each staff record's Access tab. An old bookmark to Crew Management takes you there.
    • "Stay logged in" now shows "Renewing..." while it works, and tells you plainly if your session could not be renewed and why.

    Lookup tables

    • Lookup tables now share the same page header as the other setup pages, with Add value and Save at the top, and ask before you leave with unsaved changes.
    • Values that come built in with Vigil (marked "State list") can be hidden or shown, but not renamed. Before, a rename seemed to save and then went back the next time the database was updated. Your agency's own values can be added, renamed and hidden.
    • Values are no longer deleted. Hide a value to retire it; anything already using it keeps working.
    • Lists that have their own setup page (payers, 837 routings, clearinghouses, payment categories, fund codes, programs and prevention lists) now show read-only here, with a button to open the right page.
    • Service codes from the classic KIS program are read-only here and can be hidden or shown. Change them in KIS.
    • The searches and column headings stay in view as you scroll.

    Programs

    • Programs now shares the same page header, with Add program and Save at the top. Save says what you changed, and switching or leaving with unsaved changes asks first.
    • The state's FASAMS placement types are listed apart, under "From the state's list". Only Active and Program Manager can be changed on them; their name and code show as plain text.
    • A Program Manager who has since left now stays on the program when it is saved.
    • The FASAMS code for State Mental Health Treatment Facility is now in the list.
    • Turning a state placement type off now says, before you save, how many programs report under it and that their services will be held. Turning it back on links the programs that were waiting.
    • After saving, Vigil shows its real message, including when a program saved but could not be linked to the state's list.

    Billing setup

    • Leaving Billing setup with unsaved changes now asks you to Keep editing or Discard, including when you use the links in the page header.

    Glimmers: rings around your face

    • Staff who use Glimmers now earn a ring: a frame around their photo or initials that grows as they earn Sparks.
    • There are 12 rings, from a copper rim and a gold rim through olive sprigs and a laurel wreath to a little lantern that hangs, lights and finally rises to crown the wreath. The outer rings add drifting motes and a gentle glow.
    • The motes and glow take the colour of each person's Kindled.
    • Rings show wherever staff faces appear: the top bar and My Account panel, the Staff page, and the Caseload card on a client's page. They are never printed.
    • Anyone who has turned Glimmers off shows the plain circle, as before.

    Glimmers: one level, not two

    • Glimmers now has a single level, worked out from the Sparks you earn. There are 60 levels, and a new ring arrives every 5 levels. The Gloaming titles carry on.
    • Every Spark you earn counts toward your level, including signing notes and Bright Weeks, not only honors.
    • Levels and rings never go down. Spending Sparks in the Bower never costs you a level or a ring.
    • After the update, each person's level is worked out once from the Sparks they have already earned, so the level number and title shown may change the first time. Nothing earned is lost.

    Glimmers: your ring

    • A new "Your Ring" section on the My Glimmers tab shows your ring and how far it is to the next one.
    • You can choose which ring to wear: always your newest, any ring you have reached, or the plain circle.
    • When a level brings a new ring, the level-up card shows it drawing itself around your face.
    • The first time after the update, everyone sees a one-time "Your ring, so far" moment.
    • Ring moments never appear while you are on a client's record.
  9. Vigil Rolling out One look across Vigil · Clients and services open in a new tab · Configuration · Service Entry: an easier screen · Staff page: connect a sign-in someone already has · Billing setup: add a clearinghouse · …

    One look across Vigil

    • Configuration, Service Entry, Service Search, Service templates and Billing setup now share the same page header. Save, Cancel and Add sit in that header and stay in view as you scroll.
    • Save waits until you change something, and says what you changed (for example "1 change: Description").
    • If you change a field and then put it back, Vigil no longer counts it as a change, and leaving the page does not ask.
    • Leaving a page, or switching to another record, with unsaved changes asks you to Keep editing or Discard.

    Clients and services open in a new tab

    • Clicking a client or a service anywhere in Vigil now opens it in a new browser tab, so you never lose your place. This includes Client Search, Home, Service Search, the client's Services list, the episode tree and Service Entry.
    • Menus, back buttons and Configuration rows still open in the same tab.
    • Client and service links look the same everywhere: a dashed underline, with a small new-tab icon when you point at them.

    Configuration

    • The Configuration page is arranged in five panels: Services and billing, Clinical records, Residential care, Organization, and Data and compliance. Each row says plainly what is there and opens with "Open".
    • "Control Room" is now called "Configuration" everywhere.

    Service Entry: an easier screen

    • The client's name, MRN, date of birth, program and program area now sit in the header at the top of the service, next to Save. The client's name opens their face sheet in a new tab.
    • A signed or completed service opens as a read view that shows each answer as plain text ("Not answered" when blank). Press Edit to change it.
    • The tabs stay pinned at the top as you scroll. Each tab shows a check when its required answers are complete, or a dot showing how many are left.
    • Next and Previous buttons at the bottom of each section move you through the note.
    • On a saved service, Save Draft waits until you make a change.
    • Cancel with unsaved changes asks you to Keep editing or Discard. Save Draft is always at the top of the screen.
    • Saved answers to radio-button questions, and answers carried forward, now show as selected when you reopen a service.

    Staff page: connect a sign-in someone already has

    • When you choose "They already have one" on a person's Access tab, or in the Add Staff wizard, Vigil now lists every sign-in that is not yet connected to a staff member. Before, the list stopped after the first 30 or 40.
    • A new search box filters the list by name or sign-in name as you type.
    • Likely matches come first. Vigil now also recognises sign-in names such as "jsmith" or "smithj", and the person's Staff Code.
    • A small tag says why a sign-in is suggested: Same name, Sign-in name looks like theirs, Same last name, or Old link matches this Staff Code.
    • Vigil never connects a sign-in on its own. You always make the choice.

    Billing setup: add a clearinghouse

    • The Clearinghouses tab now has an "Add clearinghouse" button at the top of the page, so an agency with no clearinghouse set up yet can add one.
    • Fill in the name and envelope IDs and save. You can then set up its outbound connection on the same screen.
    • If a clearinghouse with the same name already exists, Vigil says so and does not add a second one.
    • If an entry is too long for a field, Vigil tells you which field and how long it can be.
    • Changing a service that is already saved now follows clear rules.
    • A completed service can be corrected only by someone with the new access "Correct signed services". Directors have it. Your agency can give it to other access templates on the Access page.
    • When you correct a service that has been signed or completed, Vigil asks for a short reason.
    • A service whose claim may already have gone to the payer can no longer be changed in Service Entry. Corrections to a sent claim go through billing.
    • A service whose bill is in a claim batch that is still being built cannot be changed until it is taken out of the batch (or the draft batch is voided). Vigil names the batch.
    • When you correct a service whose bill has not been sent yet, the bill's date and amount update with it.

    Signatures cover what was signed

    • If you change the details or form answers of a signed service, its signatures are set aside and must be given again. A service entered in Vigil goes back to Draft until it is signed again.
    • Only the person who gave a signature, or someone with "Correct signed services", can change a signed service. The same rule now applies to voiding a signature.
    • A form section that has its own signature cannot be changed until that signature is voided.

    A record of every change

    • Every change to a saved service is now recorded: who made it, when, each old and new value (form answers included), and the reason.
    • A history view on the service, and an "Amended" note on the printed service, are on the way.

    Services entered in the classic KIS program

    • Services entered in the classic KIS program can be corrected in Vigil too, under the same rules. They stay posted, just as KIS posted them.
    • Changing the quantity of a completed time-based KIS service re-prices it the way KIS does: minutes / 60 x the rate. A flat-fee service keeps its flat rate. The quantity of a dose-based service, or of a service with no price set, cannot be changed.
    • Editing a KIS service in Vigil now keeps its reporting unit.

    Service Search

    • Service Search now opens on the current month, so the list loads quickly. Press Clear to search all dates.
    • The "Units" column is now "Quantity", shown with its unit (minutes, days, doses and so on) for services entered in Vigil. Services entered in the classic KIS program show the number only. The client's Services list uses the same wording.
    • Client names no longer repeat the MRN.
    • Column sorting and page buttons now work with the keyboard and with screen readers.

    Service templates

    • Templates open ready to change, with no Edit button to press first. A note at the top says "Ready to edit. Nothing changes until you press Save."
    • The template is arranged in the order you set it up: Service details (What it is, How it's counted and priced, What it requires), then Programs / Funding Sources, then FASAMS / State Reporting in its own card. The state funds that can pay for the service are now inside the FASAMS card, and the whole card is hidden when FASAMS is turned off.
    • "Default Rate" is now called "Standard Rate".
    • Switching to another template, or duplicating one, with unsaved changes now asks first. Before, those changes could be lost.
    • You can open a template from the list with the keyboard.
    • A funding source on a template can now carry its own rate, so a service can be priced differently for state funding and for Medicaid or insurance. Leave it blank to use the Standard Rate.
    • Vigil prices a service at the rate for the service's payer, or the Standard Rate when that payer has none. A sliding fee discount applies to that rate.
    • The Funding Sources table shows each rate: the funding source's own, or "Standard" with the amount.
    • Services already saved keep their current price.
    • Services entered in the classic KIS program are not affected.

    Billing setup (formerly Payer directory)

    • The page is now called "Billing setup", because it holds five tabs: Organization, Payer Directory, 837 Routing, Clearinghouses and Agency Defaults.
    • Save, and each tab's Add button (Add payer, Add category, Add routing, Add clearinghouse, Add default), now sit at the top of the page and stay in view.
    • The payer list's search and filters stay in view as the list scrolls.
    • A payer's "Payment Type" is now called "Payment category" everywhere it appears, including Service templates and client billing records. Cash Management's Payment Type (cash, check) keeps its name.
    • Choosing Discard when you switch tabs now puts the record back the way it was.
    • The FASAMS Fund Codes list has been removed from the Payer Directory tab. Each payer's own FASAMS fund code is set on the payer, as before.

    FASAMS: settings moved to where you use them

    • The separate FASAMS export settings page has been removed.
    • The file size limit is now in the FASAMS Export Center, on the Build tab under Advanced options ("Split the file over (MB)"). Administrators can change it; other staff see it read-only.
    • Re-applying fund codes is now done one payer at a time. Open the payer in Billing setup and, under its FASAMS fund code, use "Update this payer's existing services to its fund code". Press Check to see how many services would change, then Update. This shows while FASAMS is turned on.
    • Each service updated this way gets an entry in its record of changes, with the old and new fund code and the payer.

    Billing Center: Recycle

    • Recycle now prices time-based KIS services the same way KIS does, including services billed in 15-minute units.
  10. Vigil Rolling out Staff page: change a sign-in name · My account: sign-in and passphrase · Security

    Staff page: change a sign-in name

    • On a person's Access tab, an administrator can now change their sign-in name with "Change sign-in name".
    • Their passphrase stays the same.
    • The classic KIS program uses the same sign-in name, so the new name works there too.

    My account: sign-in and passphrase

    • Open My account (click your picture) and choose "Sign-in and passphrase" to change your own passphrase or your own sign-in name.
    • Vigil asks for your current passphrase first. Wrong entries count toward the usual sign-in lockout.
    • After you change your sign-in name, Vigil signs you out so you can sign in with the new one.

    Security

    • The audit trail now records each person's real network address.
    • When someone is locked out for a while after too many wrong passphrases, the audit trail now records it.
    • Error pages no longer show technical detail.
  11. Vigil Rolling out Before access is switched on at your agency · Email that works out of the box · Notifications page · Welcome email for new staff · Sign-in keys · Email security · …

    Before access is switched on at your agency

    • The built-in Clinician access template shows only clients on the person's caseload. Before access is switched on, make sure each clinician's caseload lists the clients they work with, and that each clinician's sign-in is connected to their staff record. KIS will go through this with you as part of the access setup.

    Email that works out of the box

    • Vigil now sends email without any setup at your agency. Sign-in keys, alerts and staff reminders come from Vigil's own email service and show as "{Your agency} via Vigil".
    • Replies go to the address your agency chooses on the Notifications page.
    • KIS sets the email service up once on your server. There is nothing for your agency to configure.
    • An agency that wants to send through its own email server can still choose that (an advanced setting on the Notifications page).
    • Appointment reminders to clients are not sent from Vigil's email service for now. They go out only if your agency uses its own email server.

    Notifications page

    • The Notifications page now shows who sends your email and whether it is working, and lets you send yourself a test email.
    • If email cannot be sent, administrators see an item about it on the Home page.

    Welcome email for new staff

    • The welcome email has a fresh look: the Vigil lantern, the four Kindled waving hello, and a clear "Your way in" card.

    Sign-in keys

    • If a sign-in key cannot be emailed, Vigil now tells you why.
    • A Director can show a new person's first key on screen, to hand it over in person.
    • The "Lost your key?" steps are now more secure.

    Email security

    • Email passwords are now stored sealed to your server, never as plain text.
    • Sign-in keys are removed from Vigil's email records once the email has been sent.

    Staff and sign-ins

    • "Lock out of Vigil" and "Unlock" replace "Pause" and "Resume", and a lockout now takes effect at all times.
    • "Reassign this sign-in" replaces "Disconnect".
    • Add Staff checks the Staff Code and the sign-in name as you type, so you know straight away if one is already in use.
    • The Add Staff window has a refreshed look.
    • A person's Access tab now shows just their access template, with a Change button.

    Access: caseload-only now covers the whole client record

    • An access template set to "Only clients on their caseload" now limits the whole client record, not just the Clients search. Before, a person could still open any client by number.
    • With that setting, the client record, every client screen and the client printouts (Face Sheet, Emergency Transfer Sheet, service printouts and treatment plan printouts) open only for clients on that person's caseload.
    • Opening any other client shows a calm "This client isn't on your caseload" page. It never shows the client's name.
    • Scheduling, billing and the desks still see every client. Groups and the med pass work as they do today.
    • Administrators and Directors are never limited.
    • A caseload-only template can be given only to a person whose sign-in is connected to their staff record. Vigil tells you when it is not.
    • A caseload-only template cannot include Billing, FASAMS, Configuration, or Logins and access.

    Caseload (formerly "Care team")

    • "Care team" is now called "Caseload" everywhere on screen: the client dashboard card, messages, the Face Sheet and the access setting.
    • Each client has one primary staff member, and the primary is always someone who has the client on their caseload.
    • Ending or removing the primary staff member's caseload assignment clears the primary, and Vigil tells you so.
    • Moving a caseload to another staff member moves the primary with it.

    Billing records and treatment plans

    • Reordering a client's billing records changes only that client's records.
    • Linking treatment plan objectives to a service accepts only that client's own objectives.

    Payer Directory

    • After you save a brand-new payer, or change its category or routing, the "Update clients who already have this payer?" window now says plainly "No client has this payer yet, so there is nothing else to do." when no client has it, instead of "All 0 clients".

    Coming soon: Lanterns, a new way to learn Vigil (preview)

    • Lessons are now grouped into three sets: Clinician, Configuration and Administrator. When you finish every lesson in a set, it is marked "Illuminated".
    • The administrator lessons on service templates are now titled "Service Templates".
    • A new Configuration path, "The Underwriter's Desk", teaches administrators the Payer Directory in three short lessons: - What a payer is, and what its Payment Category decides: the questions staff are asked on a billing record. - How each payer is billed or reported: only a payer set up for 837 claim files gets a bill, FASAMS XML payers are reported to the state, payer portal payers are entered by hand on the payer's site, and a payer with no channel sends nothing. - Setting up a payer for the state's FASAMS file (fund code and subcontract), and each payer's sliding fee switch.
    • Lanterns is still open only to a small group of preview testers. You will hear from us when it opens to everyone.
  12. Vigil · Desktop utilities Released Synchronize: safer database updates · Synchronize: default data for the system database

    Synchronize: safer database updates

    • Before anything is changed, Synchronize now checks that the downloaded update is complete and intact, and that it is the right kind for the database you selected (system or clinical/billing).
    • The preview report now also lists the built-in default data an update will apply.
    • If a check finds a problem, Synchronize stays disabled and tells you "No changes were made".

    Synchronize: default data for the system database

    • Synchronize can now apply Knight Software's built-in default data to the KIS system database, as it already does for the clinical/billing database.
    • The system database is shared with the KIS program and with every company database on your server, so these updates follow strict safety rules: - They only add or correct Knight Software's own default entries. They never remove or overwrite your agency's own data. - Anything that could delete data or change the database's structure is refused and never runs. - Each step is all-or-nothing. - If the database is busy, a step waits no more than 30 seconds, so sign-ins to the KIS program are never held up. - If any step has a problem, the update stops there.
  13. Vigil Rolling out Access: who sees what (new) · Staff · Signing in and staying signed in · Service Entry · Site and staff lists show only current choices · Appointment reminders · …

    Access: who sees what (new)

    • Each agency's new access controls start switched off. Nothing changes for your staff when the update is installed. KIS will help you set up everyone's access before it is switched on.
    • Configuration > Access holds access templates such as Front desk, Clinician, Billing and Supervisor. Each one says which parts of Vigil a person can see or change: Hidden, Can look, or Can change.
    • You can copy a built-in template to make your own, for example a front desk that sees only Demographics, Appointments and Documents.
    • You choose each person's template on their Staff page, on the new Access tab.
    • Once access is On, people see only what their template allows, including menus, client tabs and dashboard cards. If someone opens a page outside their access, they get a friendly note telling them who to ask.
    • Front desk staff see only the last 4 digits of a client's SSN, unless their template includes the full SSN. Saving the record always keeps the full stored number.
    • Staff credentials (licenses, DEA, payer IDs) can be limited to the people who manage them.
    • Your agency can never be locked out of its own system. KIS support and your agency Director can always reach sign-ins and settings. Every use is recorded, and your administrators are told whenever KIS support's sign-in is used.

    Staff

    • Add Staff now sets up the staff record, the sign-in and the access in one guided step.
    • Crew Management is retired. Everything it did now lives on the Staff page.
    • Sign-ins are now linked to staff by their staff code, the same way the classic KIS program does. Linking a sign-in in Vigil no longer stops the classic program from filling in the staff member for you.
    • Because the staff code now links a sign-in, two staff members cannot share a code, and a code that is linked to a sign-in cannot be cleared.

    Signing in and staying signed in

    • Every page in Vigil now requires you to sign in.
    • Client photos, documents and state report files open only inside Vigil, not from a saved web address.
    • Clinical record images load through Vigil's secure image service.
    • "Stay logged in" now works as it should. The warning appears before your session ends, and choosing to stay keeps you signed in for up to 12 hours.

    Service Entry

    • The Unsaved Changes window (Continue Editing / Discard Changes / Save & Leave) now shows its intended warm look, in Vigil's own colours, instead of a plain yellow box.

    Site and staff lists show only current choices

    • Site and staff drop-down lists no longer offer hidden sites or inactive staff. On Service Entry, for example, the staff list used to show everyone ever entered and the site list every site; now each shows only the ones in use.
    • This applies to Service Entry, Group Sessions, Bed Days, Appointments, the client's admission and discharge forms, the default site on Service Templates, and Cash Management.
    • Opening an existing record never blanks a site or staff member. The field still shows the saved name, marked "(inactive)" or "(hidden)", and saving without changing it keeps it.
    • Once you change that field, the inactive person or hidden site cannot be picked again. If an older record needs one of them, re-activate the staff member or un-hide the site briefly, make the change, then set it back.
    • A new record never starts on an inactive person or hidden site. A new discharge fills in the admitting clinician only if that person is still active, and a new service started from an appointment at a hidden site starts with the site blank for you to choose.
    • The calendar's Site and Staff filters now list current choices only.
    • Reports still list every site, so a report can reach back through your history.

    Appointment reminders

    • Appointment reminder emails now name the appointment's location.

    Something is happening (a small pilot)

    • When you click something and Vigil needs a moment, your Kindled now walks along the bottom of the screen until the work is done, then hurries home. After a longer wait it may land with a little somersault.
    • If Glimmers is off for you, a small glowing lantern makes the same walk instead. If you have asked your computer to reduce motion, it stays put and glows.
    • For now this is a pilot on Client Search and Service Entry only. We will widen it once it has been used for real.

    Glimmers: welcome home

    • The Glimmers page now opens on the Hearth, where your Kindled lives, and greets you with "Welcome home".
    • A painted Gloaming background sits behind the page. It changes from day to day.

    Coming soon: Lanterns, a new way to learn Vigil (preview)

    • Lanterns teaches Vigil inside Vigil. Your Kindled walks you through a task, asks what you think will happen, and then the practice screen shows you.
    • You practise on copies of the real pages (Home, Service Entry, the signature window). Nothing there is saved, and nothing can be typed, so no real client information is ever involved.
    • The first path, "First weeks", has five lessons: finding your way around Home, starting a note from your schedule, keeping your work safe, reading the red and amber notes, and signing and correcting a note. Each lesson lights a lantern and adds a piece to a keepsake.
    • Each lesson ends with an "At your agency" card for the things your agency decides, not the software, such as signing deadlines.
    • A first look at a path for administrators, on service templates, is also in preview.
    • Lanterns is open only to a small group of preview testers for now. You will hear from us when it opens to everyone.
    • Behind the scenes, Vigil now quietly notes when you save or sign a service, so lessons can later recognise work you already know. It records no client information and changes nothing on screen.
  14. Vigil Rolling out Reports Workshop: simpler filters · Reports Workshop: which site? · Reports Workshop: more accurate results · Reports Workshop: exports · Reports Workshop: new conveniences · Reports Workshop: Yes/No columns · …

    Reports Workshop: simpler filters

    • Lists are now searchable checklists you tick; no more Ctrl-click.
    • A value a field cannot use is flagged before you run, with a short note saying why.
    • A filter still waiting for its value is marked and left out until you fill it in, so it never quietly counts everyone.

    Reports Workshop: which site?

    • Site Code (for example 2H or 2I) is now available.
    • Every site field says which site it means: where the service was delivered, the admission's site, or the appointment's site. Hover over a field for a short explanation.
    • These can give very different answers (in one real report, 34 clients by service site but 14 by admission site), so pick the one you mean.

    Reports Workshop: more accurate results

    • "is" with several values now matches any of them.
    • "is not" keeps records where the value is blank.
    • Date filters include the whole last day.
    • A report you have filtered no longer quietly shows only the last 12 months when it has no dates. When a report with no filters at all does use the last 12 months, it says so.
    • "Units" is now labelled "Units Entered (minutes, doses or days)", and a new "Billed Units" field shows the billed units for services priced in Vigil.

    Reports Workshop: exports

    • A "top 10" report exports exactly 10 rows.
    • Large exports now arrive as one complete CSV file instead of stopping at 50,000 rows.

    Reports Workshop: new conveniences

    • New All time, This FY and Last FY date buttons.
    • "Show each row once" gives a clean client list, and the Workshop offers it when names repeat.
    • A new "Client List by Site" recipe.
    • Undo after clearing a report, changing the subject or removing a filter.
    • When a report finds nothing, it shows which filter is responsible and lets you remove it.

    Reports Workshop: Yes/No columns

    • A new "Who Overlaps Between Sites?" recipe gives one row per person with a Yes/No column for each site you pick (a dot means yes). Under the total, it counts how many said yes to each site and to all of them.
    • On any People report, you can now show a condition as a Yes/No column for everyone instead of using it as a filter: choose "add a Yes/No column". You can also make one column per picked value.
    • Column headings name the date window, so "No" means none in that window.
    • Site filters are noticeably faster.

    Glimmers: honors for building reports

    • New Glimmers honors for building reports in the Workshop: saving your first report, trying different recipes, taking the Genie's advice to fix a number, using "Why zero?", asking a Yes/No overlap question, and when teammates run a report you shared. A couple are surprises.
    • Nothing is earned by exporting or by running reports over and over.
    • Honors appear quietly, never in the middle of building a report. Staff who have turned Glimmers off see nothing.
  15. Vellum Released CCBHC: SAMHSA reporting workbook · CCBHC: new Epic imports · CCBHC: Depression Screening and Follow-up (CDF) · CCBHC: Depression Remission (DEP-REM-6) · CCBHC: Time to Services (I-SERV)

    CCBHC: SAMHSA reporting workbook

    • A new Export button in the Measure readings panel fills in SAMHSA's own CCBHC Data Reporting Template from your recorded measure readings. Vellum fills only the input cells. SAMHSA's formulas, layout and checks stay exactly as SAMHSA wrote them.
    • If the reporting period has not been locked yet, the file is marked DRAFT.
    • Before you download, Vellum lists anything it could not fill. The list is grouped by what it takes to close each gap: waiting on data, needs a decision, still to build, or disclosed in the notes.
    • Adherence answers and Additional Notes are drafted for you from your measure definitions and each reading's own checks.
    • The workbook covers Case Load (including insurance status), Depression Screening and Follow-up (CDF), Depression Remission at Six Months (DEP-REM-6), Unhealthy Alcohol Use Screening (ASC), Social Drivers of Health screening (SDOH), and the Time to Services (I-SERV) measures.
    • The same payer rules now apply on every tab. Dual-eligible plans count as Non-Medicaid, and no payer on file counts as uninsured. Declined or unrecorded military status is reported as Neither. Each tab's notes state these rules.

    CCBHC: new Epic imports

    • Data Import now accepts three more Epic files: the problem list, the CMS-2 depression screening lists, and the DEP REM Reporting Workbench export.
    • The data sources card explains what each file is and how often to pull it. The freshness strip shows when each one was last imported.

    CCBHC: Depression Screening and Follow-up (CDF)

    • Results now come from Epic's CMS-2 lists, split into ages 12-17 and 18+.
    • Anyone ever diagnosed with depression or bipolar disorder is excluded, as SAMHSA requires. Vellum checks the problem list and visit diagnoses for this.
    • The rate is shown once the CMS-2 "Not In" list is imported. Until then you see the numerator and a note explaining why there is no rate yet.

    CCBHC: Depression Remission (DEP-REM-6)

    • Counts everyone on the CCBHC roster, wherever the PHQ-9 was taken.
    • A starting visit needs a qualifying depression diagnosis. People with bipolar, personality or psychotic disorders, pervasive developmental disorders or palliative care are excluded.
    • PHQ-9 history now goes back to December 2023 through the Reporting Workbench data.
    • If someone has two PHQ-9s on the same day, the higher score counts. Those days are listed for manager review.
    • Age is now taken on the day of the screening instead of today.

    CCBHC: Time to Services (I-SERV)

    • Clients under 12, or with an unknown age, are no longer counted as adults.
    • Crisis unit demographics and payer now come from Credible, the crisis unit's own system.
  16. Vigil Rolling out Services · Appointments · Home page · Client page · Forms Designer · Glimmers: your Kindled is alive · …

    Services

    • Services that need no signature (for example a prescription incidental) can now be finished: a new "Complete & Post" button posts the service, and bills it when its payer is billed.
    • Such a service shows as Draft until you click Complete & Post, and Complete after.
    • Action Items list these services as "Ready to post", and no longer list posted services as "Unsigned service".

    Appointments

    • Opening a service from an appointment fills in the minutes from the appointment's booked length when the visit has one service. When a visit has several services, the booked time is shared, so enter each service's minutes yourself.
    • A small icon and line beside a prefilled number say where it came from: the appointment or the service template.
    • Medication incidentals (dollar-amount services) and inactive services no longer appear when choosing services for an appointment.

    Home page

    • Today's schedule is now at the top left and loads first, with Action Items below it.
    • Recent Clients (on the home page and in client pickers) now shows only clients you actually opened.

    Client page

    • The header shows the client's phone number, with an icon for mobile, home or work, and keeps showing it after the page is reloaded.
    • Home phone numbers are now saved in the format the KIS desktop system and state reporting expect.
    • "Documents" is now "Document Uploads", and "Services" is now "Services & Notes".

    Forms Designer

    • A checkbox question can carry its own text (for example "Positive"), shown beside the box and on printouts ("Positive: Yes").

    Glimmers: your Kindled is alive

    • Glimmers, Vigil's staff-delight feature, gets its biggest change yet. The corner companion is now a living, animated creature, not a picture. It breathes, blinks and looks around, hops when you tap it and leans in when you pet it.
    • It comes closer when something goes wrong, cheers quietly when the error is fixed, and grows drowsy in the evening (Veyl never sleeps). Each of the four Kindled has its own personality.
    • It steps aside on heavy clinical screens and under dialogs, can be tucked away to a small glowing dot, and uses almost no computer power.

    Glimmers: meeting your Kindled

    • The meeting ceremony no longer starts on its own. Staff without a Kindled see a small invitation: "Something small and bright has noticed your work. When you have a quiet moment, come and meet it." with "Meet it" and "Not now".
    • "Not now" rests the invitation for a week, then a month, and after the third time it stops. The Hearth always keeps the door open.
    • Staff who have turned Glimmers off are never invited; their Hearth simply says their Kindled is still near.
    • Staff whose Kindled was here before the new companion get a one-time note that it has stirred, and where any retired pieces are kept safe.

    Glimmers: calm celebrations

    • Glimmers never interrupts your work. No celebration appears while you are typing, while a form has unsaved changes, or under a dialog; it waits for a quiet moment.
    • Most honors now arrive as a small glowing light beside your Kindled. Open it to see what your Kindled kept for you, each with its own line of story.
    • Bigger honors still get a card. Several from the same day share one card, and there are at most three cards in a session. Cards never close by themselves and work with the keyboard and screen readers.
    • Muting Glimmers also turns cards into the quiet light.

    Glimmers: Sparks and honors

    • Sparks now trickle in from everyday work: 1 for each note you sign.
    • Every Spark is kept in a ledger, so balances stay exact.
    • About 20 new honors, many told from your Kindled's point of view.
    • Honors for past work now pay Sparks once, and several honors that could not be earned before can now be earned.

    Glimmers: Bright Weeks (directors and supervisors)

    • A new Bright Weeks tab on the Glimmers page lets you light a week for the whole agency or chosen programs, see the weeks, and end one. During a Bright Week, timely notes earn extra Sparks.
    • Before lighting one, you see whether people are signing notes in Vigil with Glimmers on.
    • While a week glows, the Hearth glows and names it. Afterwards you see a picture of how the grove glowed, never a number, and nothing at all for very small groups, so no one can be picked out.

    Glimmers: the Hearth and the Bower

    • The Hearth is now your Kindled's nook: a little room you can decorate. Dress your Kindled with a hat, a face piece and something in each hand, or offer it a treat. A different line each day says what it was doing when you arrived.
    • The Bower has a Halloween collection for October: Witch's Hat, Starlit Mask, Candy Bucket and Little Broom, plus Pumpkin Pile, Paper Bat Garland and Candle Cluster for the nook.
    • You can try a piece on your own Kindled before you buy it. When you buy, your Kindled turns to show it off.
    • The old paper-doll items are retired, because the new companion cannot wear them. Anyone who owns one keeps it, under "Kept safe". If a design is redrawn for the new companion, owners get it automatically.

    Glimmers: privacy, access and fixes

    • Turning Glimmers off is now respected everywhere, including the Team Wall and play in the Hearth.
    • The Kindled chat is protected against message tampering, and purchases and wardrobe changes are recorded in the audit log.
    • Keyboard play, focus, screen-reader labels and Ctrl+P printing all work better.
    • Tapping the companion now plays with it, instead of sometimes opening notifications.
  17. Vigil Rolling out Record Health and Readiness (client page) · Validation Worklist (new, in the Services menu) · Inbox - "Waiting on you" · New checks · What goes to the state (FASAMS) · POMs, evaluations and Assessments are entered as services · …

    Record Health and Readiness (client page)

    • The Record Health card now lists what is waiting on the record and who it is waiting on.
    • Clicking it opens a side panel laid out by client, then each episode (Program, Admission POM, Evaluation, Diagnosis, Discharge POM), then services. Each item has a Fix button.
    • Fix buttons open the right screen, episode and section, put the cursor in the field that needs attention and highlight it. Demographics opens for editing when you are allowed to edit.
    • Fix buttons open in a new tab, so the page you were working on keeps your place and anything you typed.
    • "Staff has no education level" opens that staff member on the Credentials tab, ready to set Education Level.
    • Race, ethnicity, gender, county, referral source and co-dependency can be answered right in Record Health: choose from the list and Save. The item clears when the answer is right.
    • "Check again" re-checks the client on demand.
    • The FASAMS badge in the client header shows how many FASAMS items are open.
    • Missing pieces the state needs are shown as "next up", not as errors.
    • "All clear" is shown only when the record passes the current rules.
    • Staff who do not handle state reporting no longer see FASAMS-only items counted against them ("Nothing waiting on you."). Deleted clients no longer count in a caseload.

    Validation Worklist (new, in the Services menu)

    • Every open item in one place: My items, Configuration (settings that affect many records - fix once), FASAMS proof run, and Everything.
    • Group by rule or by record, filter by client, and export to CSV.
    • Administrators get a "Check everything" button for the fiscal year. It shows live progress, can pause and resume (even after you leave the page), says "All done", runs gently, and re-checks records checked before a rule changed.
    • Staff see only what is theirs. Clinicians and front-desk staff no longer see state-reporting (FASAMS) items. Read-only accounts can look but not re-run checks.
    • On phones, filters open in a "Filters" sheet. Totals count up, the page number is kept in the address, and a failed load offers "Try again".

    Inbox - "Waiting on you"

    • After "Check everything" or a FASAMS build's check finishes, each person gets one inbox message saying how many items are waiting on them, with a link to My items. It never names a client, and it updates instead of piling up.

    New checks

    • New checks are first shown as "New check, not enforced yet" and counted separately on the client card (for example "2 to fix early"). The header badge counts only checks that are enforced.
    • Client: an SSN that is never issued; a pseudo-SSN that does not match initials and birth date; characters the state does not accept in a name; a zip, state or county the state would reject; a Medicaid ID used in place of an SSN; a birth date more than 150 years ago.
    • Service: dated after the episode's discharge; linked to a deleted episode or program, or dated outside its program; entered twice; a site, OCA, setting or county the state file would leave blank; a covered service used on the wrong kind of service; two day services for one client on one day.
    • Subcontract: each service is checked against its payer's subcontract lines (OCA, covered service, program area, project). The line must be active and in force on the service date; an expired or deleted line says "renew or correct that line". Each missing line appears once on the Configuration view, with its record count and a button that opens the subcontract in the Drawdown Optimizer. This check stays a warning for now.
    • Programs and placements: overlapping FASAMS placements; placement dates and outcome; a program and its placement that disagree; a program type with no FASAMS code; admissions of one program area that overlap; a service outside its program's placement.
    • Warnings that show what the state file assumes: staff with no education level; a POM substance with no route, frequency or age of first use; a POM or evaluation with no staff of its own; a substance abuse admission whose co-dependency is Unknown; a days-waiting value below zero.
    • Fixing one service of a duplicate or same-day pair clears the other right away.
    • Fewer false items: payments, write-offs and other ledger entries are no longer checked as services; "Admission type is required" is gone; the old admission checks on primary drug, route, frequency and age of first use are gone (substances are reported on the POM); the non-client placeholder is no longer checked for demographics.

    What goes to the state (FASAMS)

    • An episode goes to the state only when it is complete: an admission POM, a level of care and a level of functioning at admission, a diagnosis, a FASAMS placement, a program area, site, primary clinician and referral source; and, once discharged, a discharge POM and discharge level of care (not needed for a discharge for lost contact or death).
    • A problem with an episode's placement, POM, evaluation, diagnosis or discharge holds the whole episode. A problem with one service holds only that service.
    • Whole episodes are sent: every episode admitted in the period, or open during it, goes complete with its FASAMS placements and client record, when it has at least one service for a FASAMS payer.
    • A service is sent only when its FASAMS payer's billing record covers the service date.
    • A service whose FASAMS placement has not been sent yet waits for the file that carries its episode. The preview says so ("nothing to fix").
    • Services from an Immediate Discharge now reach the state. Deletions still reach the state, always in a separate deletions file.
    • Before every preview, validation and build, Vigil re-checks every record in that build. The button shows the progress ("Checking records 1,200 of 12,400"), the build waits until the check is done, and a record that cannot be checked is named instead of guessed.
    • Once your agency is switched over, Vigil's checks decide what is held, and saving a record in the KIS desktop system can no longer quietly release something Vigil is holding.
    • Run Validation shows what keeps records out of the next file, one line per reason with how many records it touches, or "All clear". The preview counts every held episode and says how many services are out and why. Posted services with no payer are split into desktop-system services and Vigil services, each with what to do.
    • Services entered in Vigil now record whether they are direct or indirect (prevention is always indirect), so they can reach the state file and the Drawdown Optimizer. The Drawdown Optimizer counts exactly what the file carries.
    • Every service now tells the state where it happened: its treatment locale comes from its service template (Service Templates > FASAMS card) and its county from its site. Insurance claims keep the place of service they had.
    • New: the managing entity's error list (FASAMS > Alignment). Upload the "FASAMS Errors" workbook your managing entity sends back; each error is matched to the record it names, beside what Vigil's checks say about that record today, grouped by error with counts. It is checked against your Federal Tax ID, nothing is saved, and it never holds or clears anything.

    POMs, evaluations and Assessments are entered as services

    • Service templates carry a FASAMS role: Admission POM, Update POM, Discharge POM, Level of Care, Level of Functioning, Intake Assessment or Discharge Assessment - one per role and Program Area. A clash is refused and named.
    • These are records for the state, not billable services.
    • Built-in, locked forms arrive with the update: FASAMS POMs, FASAMS Evaluation, and two Assessments. The Intake Assessment records the admission POM, level of care and level of functioning in one service; the Discharge Assessment records the discharge POM, level of care and, if wanted, level of functioning, dated the discharge date.
    • Saving is all or nothing, with the same checks the state makes on the service date. The evaluation asks only what the chosen tool needs.
    • A POM or evaluation must belong to the client's admission. A discharge POM is dated the discharge date and counts only for the discharge sent to the state.
    • "Add the Admission POM", "Add the Update POM", "Add Level of Care" and similar buttons open the right form, or the Assessment when your agency uses it. If no template is set up yet, administrators are sent to set one up instead of seeing an error.
    • A new POM fills in what carries over from the admission's latest POM (veteran status, marital status, education, disability, insurance, substances and similar) and leaves blank what must be asked fresh each time (income, pregnancy, school and work days, living arrangement, frequency of use, arrests, Marchman and Baker Act). The screen says when it has filled answers in.
    • POM Yes/No questions (risk of emotional disturbance, voluntary treatment, legally incompetent, committed to juvenile justice, Marchman and Baker Act) are now Yes / No choices that start blank, and a POM cannot be signed until each one that applies is answered. Before, an unticked box was sent to the state as "No".
    • Evaluations are entered only through the state forms. A custom form that still sends answers to an evaluation the old way is refused when saved, with a message saying so.
    • POM and evaluation answers marked for the Golden Thread appear there, and scored ones appear in Trends.

    Discharge, programs and FASAMS placements

    • Discharge is one dialog: dates, staff, reason, destination, type, and an outcome per program. It records the discharge the FASAMS file sends, explains any refusal in place, and offers Immediate Discharge when it fits.
    • The discharge dialog lists each open FASAMS placement with what happens to it and where the client is going next. Programs end on the discharge date and record "discharged from the agency".
    • Correcting a discharge moves the programs and the episode with it. Moving it earlier is refused while a placement or program still ends after it, and the message names it.
    • Programs and FASAMS placements are now separate. Adding a program opens its FASAMS placement automatically, or uses the one already open, including one opened in the KIS desktop system.
    • Ending a program has its own dialog and asks why it ended: completed it, moved to another program, left before completing, or program closed / other. The reason shows beside the ended program. When it is the last program in its placement, it asks "Where is the client going next?" with nothing preselected.
    • Each episode shows its programs and, separately, its FASAMS placements, with whether each has gone to the state.
    • Billing and FASAMS staff can keep FASAMS placements up to date from the episode: change dates, reopen, correct where the client went next (with a reason), or remove one that never reported anything. Each change is checked against the state's rules and recorded in the audit trail. Clinicians see placements read-only.
    • Every service entered in Vigil (Service Entry, group sessions, bed days) records the program it was delivered under, and links to that program's FASAMS placement when the placement covers the service date. A client service now needs its program.
    • Configuration > Programs: changing a program type's FASAMS code is refused while clients are open in it; giving a type its missing code links its open programs.
    • New report: Aging Programs & FASAMS Placements (Reports > The Workshop) lists every open program and placement, longest without a service first, beside the review day for its type, including Due for Review.
    • Starting a client's second episode in Vigil works again, and the client header updates right after a new episode or program is added.

    Admissions

    • Every admission now reports its subcontract and contract to the state, from the site's Subcontract (Configuration > Sites), using the subcontract year that covers the admission date - nothing needs changing at the new fiscal year. Sites warns when the chosen subcontract has no line for this fiscal year.
    • An admission with no subcontract or contract is held, with the way to fix it.
    • Days Waiting and Co-Dependency are asked, never assumed. Days Waiting takes a number or "Unknown"; Co-Dependency takes Yes, No or Unknown and is required for a substance abuse admission. Unknown is reported to the state as unknown.
    • The admission date is required and cannot be in the future, before the intake, or after the episode's first program, FASAMS placement or service.
    • Saving an admission no longer erases fields you did not change (admission type, substance-use answers, program area, site, discharge status), and emptying a field really clears it.
    • Referral source can be set and corrected after the admission is created. Primary substance, route and frequency are chosen from lists by name.
    • A stored value the list no longer shows (an inactive staff member, a hidden site) is kept and labelled instead of being blanked on the next save.
    • Discharged episodes can be opened and corrected again.
    • A new admission of a program area cannot start on or before the day the previous one of that area was discharged.

    Forms Designer - state forms (Configuration > Clinical Records)

    • A form pack is either a custom form or a state form that saves to a state report (POM or Evaluation). Each question on a state form names the field it saves to.
    • Only an administrator chooses the kind of form, and only before questions are added.
    • A state form with a question that has nowhere to save says so in red at the top, with a link to the question. Clinicians never silently lose an answer: saving is refused and the question is named.
    • State forms lock once services are documented on them, can be given a new version, and can carry answers forward from the client's last signed one within the same admission.
    • Once answers are saved in a field, its question cannot be removed, hidden, moved or changed to another kind of answer. Its wording can still change.
    • Import and export now keep everything about a form, including its kind, fields, Golden Thread role, signer role, AI Lantern setting and advanced visibility rule.
    • A "Reportable Metric" chosen in the Designer now reaches the Trends report.
    • When two linked questions update the same client field, the one answered first wins, and a blank one no longer erases the other's answer.

    Add Client

    • The duplicate check finds an existing client by Social Security Number again, including inactive clients, whatever separators were typed.

    Billing page - Claims card (billing staff)

    • A new Claims card shows claims by status, what payers still owe on claims that were sent, what has not been sent yet, and the ten most recent claims with a link to each service.

    Sites (Configuration > Sites)

    • Sites have County and Subcontract fields. Only administrators can change or delete a site.

    Access

    • Read-only accounts can no longer change a client's demographics or photo, discharge, edit an admission, end a program, post bed days, record group sessions or change rosters.
    • Billing and front-desk roles can no longer save services. A role that can view but not save services sees the service read-only, with a note saying why.
    • Only administrators with configuration rights can change program types.

    Fixes

    • Signing now works at sites where Sign & Complete showed a "connection issue".
    • Number answers on POMs (household size, income, days, ages of first use) are now saved. A decimal where a whole number is needed is refused, and the message names the question.
    • A POM or evaluation can be saved a second time, and reopening one shows only the questions for the admission's program area.
    • Printed POMs and evaluations show answer names instead of code numbers.
    • A site-built POM form that leaves out a required Yes/No question now saves.
    • Creating a new version of a form works again.
    • A discharge POM entered later clears "discharge POM missing" right away.
    • Printed services show minutes and billed units correctly ("30 minutes (2 billed units)").
    • The Golden Thread no longer fails on a very long stay.
    • The FASAMS Validation grid's record links work again.
    • Saving a client, service or episode is recorded in the activity log against the right record and client.
    • Indirect services are no longer asked for a program.
    • Validation hints read as words, and the FASAMS SRI-type choice is easy to see and works with a keyboard.
    • Appointments, the dashboard, inbox reminders, Service Search, the residence roster and the analysis reports read programs from the new place. Service Entry now says "Program" instead of "Placement".
    • The reports' Days Waiting field leaves Unknown out of averages.
    • Side panels (Record Health and others) no longer turn the rest of the screen black. The page behind is softly dimmed, as behind a dialog.
  18. Vigil Rolling out FASAMS - record checks · FASAMS - menus and pages

    FASAMS - record checks

    • If Vigil briefly cannot tell which of your validation checks are turned on (for example, for a moment while the system is starting up), it now leaves the record's last check result as it was instead of marking the record as having no problems.
    • Before a FASAMS file is built, any client Vigil could not re-check stays marked as needing a check, so the file waits for that client instead of sending a record that may not be ready.

    FASAMS - menus and pages

    • If the FASAMS menus and pages are hidden for a moment while Vigil starts up, they now come back on their own within about a minute.
  19. Vigil Rolling out Client page - Episodes · Crew Portal - operator roles and module overrides (administrators) · Activity log

    Client page - Episodes

    • You can now start a new episode for a client whose episodes are all closed.
    • You can also start an episode for an existing client who has an intake recorded in the KIS desktop system but no admission yet.
    • When the client already has an intake from the desktop system with no admission, the new episode continues that intake instead of creating a second one. The wizard says "This continues the intake recorded on" and the intake date, and the episode date cannot be earlier than that intake.
    • The page no longer asks you to close the current episode when there is no open episode to close.

    Crew Portal - operator roles and module overrides (administrators)

    • Changing an operator's Role or Module Overrides now confirms that the change was saved.
    • If a role cannot be saved, Vigil now tells you why, for example that only administrators can assign roles.
    • After a role change, the screen now shows the new role right away.
    • Vigil now checks the role you pick and the 255-character limit on Module Overrides, with a clear message if either needs fixing.

    Activity log

    • Opening a page no longer adds an entry to the activity log just for showing your own badge, so the log is easier to read.
  20. Vigil Rolling out Billing - a bill only for payers billed by claim (action needed before this update) · Billing Center - Needs Attention · Retrieve Legacy Services · Each service is finished where it was created · Service page - billing card · Bill a different payer · …

    Billing - a bill only for payers billed by claim (action needed before this update)

    • Vigil now creates a bill only for payers set to send 837 claims in the Payer Directory (Underwriter's Desk).
    • Payers set to FASAMS state reporting, a payer portal, or Self Pay get no bill. Their services go to the FASAMS file, are submitted on the payer's portal, or go to the client's balance.
    • A payer with no submission channel set shows "Payer setup needed" instead of Vigil guessing. Once the channel is set, its services can be billed.
    • Action needed: before this update is installed, please review the submission channel on every payer in the Payer Directory. We can run a readiness report for your agency that lists any payer still needing a channel. Until a payer's channel is set, Vigil creates no new bills for it.

    Billing Center - Needs Attention

    • New "No bill needed" items are bills on payers that do not take claims. Remove them one at a time, or all together after you confirm each payer. A removed bill is kept on file, never lost.
    • An unsent extra bill for a service that has already been billed to another payer can be removed the same way.
    • New "Payer setup needed" items are bills whose payer has no submission channel yet.
    • New "Sent bill" label marks a bill that may already have gone to a payer. These bills are never removed.
    • New "Check first" badge marks a claim that may already be with one payer while its service now names a different payer. Both payers are named. Check with the payer before changing anything. These claims cannot be moved, re-checked or removed from this list, and the service is held out of the FASAMS file until it is settled.
    • Bills for client charges, and bills for services deleted in the KIS desktop system, are never claimed. If one has not been sent, a Remove bill button removes it, and the removed bill is kept on file.

    Retrieve Legacy Services

    • Brings in services for payers billed by claim, and only services that have been posted in the KIS desktop system.
    • The preview now shows what was left out and why: the payer needs setup, the payer does not get bills by design, the billing record does not cover the service date, the service has no billing record, or the service is not posted yet in the desktop system (post it there, then retrieve again).
    • Client charges from the desktop system (client fees, co-pays and similar) and services deleted there are never brought in.
    • The preview also counts services priced at $0 in the desktop system. These have nothing to bill, which is normal.

    Each service is finished where it was created

    • Services entered in the KIS desktop system are completed and posted there, then submitted through Vigil. Signing one of these services in Vigil no longer posts it.
    • Services entered in Vigil are created, signed and submitted in Vigil.

    Service page - billing card

    • When a service has no bill, the billing card says why, for example "No bill - FASAMS" or "not posted yet in the legacy system".
    • When a signed service can be billed, a new Create bill button creates its bill.
    • Signing a service, posting bed days and signing a group session now tell you why no bill was created, when none was.
    • A service entered in Vigil with a $0 charge no longer creates a bill. The service shows a warning so the charge can be corrected, and claim checking stops any $0 bill for a Vigil service.

    Bill a different payer

    • Moving a service to a payer that does not take claims removes its unsent bill. The button reads "Move and remove bill" so you know before you confirm. A bill that may already have been sent is not removed.
    • Moving a service to a payer billed by claim creates its bill if it did not have one.
    • Each payer card shows how that payer is billed: "No bill - FASAMS / portal / client pays" or "No channel set". Moving to a payer with no channel waits until the channel is set.
    • A bill that names a different payer than its service can now be corrected: pick the service's own payer to move just the bill.

    Claims and batches

    • The date a claim is sent is now recorded when a batch is marked submitted or uploaded. During the update, the sent date is filled in for claims already in submitted batches.
    • Voiding a batch that may already have been sent keeps a record that its claims may have gone out, so those bills are never removed or treated as new. Bills from earlier voided batches are marked the same way during the update.
    • A batch can no longer be uploaded twice by accident.
    • A batch that holds a bill for a payer that does not take claims, or a bill whose service now names a different payer, will not build or upload. The message says why and what to do next. Marking such a batch as submitted still records it, with a warning, because the file may already have gone out.
    • When the clearinghouse rejects a batch file, its claims come back to be corrected and sent again instead of staying stuck in the batch. When a payer's claim status report rejects individual claims, just those claims are released, still marked Rejected, ready to correct and resend.
    • Claim checking now stops a bill for a service that was deleted in the KIS desktop system, or that is not posted there. Nothing is removed automatically.
    • Billing actions such as retrieving, batching, building, submitting, voiding and checking claims now confirm that you have billing access.

    Write-offs and the Aging list

    • Write-off is available only for claims that were sent to a payer. For a bill that never went out, Vigil explains there is nothing to write off.
    • The Aging list shows only claims a payer was sent or has answered, with their balances, and tells you how many open bills are not yet with a payer.

    Voiding a signature, bed day or group session

    • Voiding removes any unsent bill, which is kept on file. If a bill may already have gone to the payer, voiding a signature puts that bill on hold instead of leaving it ready to send, and a bed-day or group void is not allowed.
    • Clicking the void button twice now voids a signature only once.

    Ledger and reports

    • A new "No Bill Needed" stage in the Ledger shows services whose payer does not get bills. They are not counted as unbilled.
    • The eligibility report no longer lists these services as never billed.

    Service templates - where the OCA and project code come from

    • Each service template now chooses one place its OCA and project code can be overridden: by funding source (on Payers Allowed) or by program (for example, Residential Level 2). A template uses one or the other, never both, so it is always clear which setting applies. With neither, the template's own codes are used.
    • Switching a template from one to the other shows how many settings will be cleared and asks you to confirm first.
    • A new "How was this decided?" explainer on the template and on each service shows, in plain words, where the OCA and project code came from.
    • Rate, procedure code and modifiers are now set only on the template. The per-payer rate, procedure code and modifier settings and the per-program rate are no longer on the screens. Anything already entered there is kept on file.

    Service templates - changes over time

    • A template keeps one current setup. There are no dated copies to manage.
    • When you save a billing change to a template, Vigil records it and asks "When does this take effect?" The question stays on the template page until it is answered.

    Editing a saved service

    • Editing a saved service no longer changes its charge unless you change the quantity or the service date, or the service had not been priced yet.
    • A blank procedure code or covered service is filled in from the template when you save. Codes already on the service are never replaced.
    • A saved service keeps the template it was entered with. If one was entered on the wrong template, your billing team can correct it.
    • Services entered in the KIS desktop system are not re-priced or re-coded when edited in Vigil.
    • If Vigil cannot work out the charge when you save an edit, it tells you and does not save, rather than saving a $0 charge.

    Claim checking

    • New warnings help your billing team review services. They never block a claim: - A service delivered on one side of a template change's effective date but entered on the other. Ask your billing team to review its charge and codes for the date it was delivered. - A service whose OCA is not on the subcontract's budget for that year. - A template set to choose codes by program, where the service's client was not in a matching program on that date, so the template's own OCA and project code were used.

    Cash Management

    • Cash Management now uses the service template's rate.

    FASAMS reporting to DCF - which services are reported (action needed before your first FASAMS build)

    • Whether a service is reported to the state is now decided by one setting: the payer's FASAMS XML box in the Payer Directory. This applies to every service, whether it was entered in Vigil or in the KIS desktop system.
    • The fund code reported is the payer's fund code from the Payer Directory. If the payer has none, the service's own fund code is used. If there is neither, the service is held and listed for you to fix.
    • Services whose payer is not set to FASAMS XML, and services that name no payer, are not sent. The FASAMS preview tells you how many services name no payer, and how many are held for a missing fund code or a "Check first" claim.
    • Client charges are never reported to the state.
    • Action needed: before you build your first FASAMS file after this update, tick FASAMS XML and set a fund code on every payer whose services belong in the state report. A payer left unticked has none of its services in the file.
    • The fund code on/off switches in the Payer Directory are gone; the payer's FASAMS XML box replaces them. The Fund Codes card is now a read-only list.
    • The Drawdown Optimizer counts the same services the FASAMS file carries.
    • The FASAMS badge on the client page now shows.

    FASAMS reporting to DCF - client file

    • The FASAMS client file now matches what the KIS desktop system has always sent, so DCF will accept it.
    • Social Security numbers are sent as digits only, and pseudo-SSNs are sent marked as pseudo-SSNs.
    • County codes are sent with their leading zeros.
    • An address is sent only when it is complete.
    • Clients whose information DCF would reject are held back, along with their services, and listed for you to correct.
    • Only clients who received a FASAMS-reportable service are included.

    FASAMS reporting to DCF - treatment episode file

    • The FASAMS treatment episode file now matches what the KIS desktop system has always sent, so DCF will accept it. Diagnoses are sent as ICD-10, placements are sent with a valid code, evaluations include their type and tool, and Yes/No answers are sent when the answer is "No" instead of being left blank.
    • Codes are sent in the two-digit format DCF expects, substance use entries are ranked in the right order, and staff are filled in the same way as the desktop system.
    • Discharges now reach DCF even when the client's last service was in an earlier reporting period, so a closed episode no longer stays open at DCF. This applies only to episodes DCF already has, so no new client information is shared.
    • Programs such as MAT or Deflection are not sent to DCF as placements for now. Your FASAMS placements are still sent. How programs should appear in FASAMS will be decided separately.

    Missing dates

    • A missing date is now left blank instead of showing as the year 0001. This applies to the FASAMS files (including service start times, which no longer go out as "0000"), staff start and end dates, dates in the EDI Billing Center, the "Modified" column in the Agency Defaults export, and other screens and exports.

    Claim and eligibility checking

    • The "Missing Patient Date of Birth" claim check now catches claims for clients with no date of birth. No current bills were affected.
    • The "eligibility check is stale" warning no longer appears for coverage that has simply never been checked.
  21. Vigil Rolling out Insurance payments (remittance / 835 files) · Bill Next Payer (new) · Write-offs · Claim checking · Reports Workshop

    Insurance payments (remittance / 835 files)

    • Payments from insurance remittance files now post to the right claims. Each payment is matched to the claim by the claim number Vigil sent, and is recorded for that claim's client.
    • After posting, each claim shows Paid, Partly paid or Denied, based on what the payer reported. A payer reversal on its own puts the claim back to Submitted rather than Denied.
    • Importing a remittance file now just reads it in. Payments are recorded when you choose Post Payments.
    • A remittance file can never post twice, even if the same file is imported again.
    • If a remittance file cannot be read, the import now tells you so instead of reporting success.
    • If some claims in a remittance were not posted, you can post that remittance again later.
    • We will help you post remittance files that were imported before this update.

    Bill Next Payer (new)

    • A new Bill Next Payer button on the Remittance (835) tab of the Billing Center. After a payer denies a claim, it shows you, client by client, what will happen next - before anything changes: - New claim - a new claim to the client's next insurance for the original charge. It is not sent until you batch it. - Reported to ME - the service moves to the Managing Entity and is reported through FASAMS. - Submit on portal - the next payer takes claims on its own website, so you submit it there. - Client balance - the balance moves to the client. - Needs attention - Vigil could not safely decide, for example when two payers have the same Payment Priority. The reason and how to fix it are shown.
    • The next payer is one whose coverage is in force on the date of service, that is on the service's Payers Allowed list, and that has not already been billed for that service.
    • Pick the bills you want to move and confirm. Nothing changes until you confirm.
    • When this update is first installed, new claims to a second insurance stay switched off until they have been tested with the clearinghouse. Until then those bills show as Needs attention.
    • Bills that have moved on show as "Moved On" in the Ledger, and as "Moved on" with a short closing note on the service's billing card.
    • Tip: setting Payment Priority on each client's billing records lets Vigil choose the next payer for you instead of asking.

    Write-offs

    • Writing off a balance works again. If any of the bills you picked cannot be written off, Vigil tells you which ones and why.

    Claim checking

    • Checking claims never removes a service's state funding code. Services entered in the KIS desktop system keep the funding code they were given there.
    • Re-checking claims no longer puts a claim that has already been sent, paid, denied or put on hold back into the ready-to-send list.

    Reports Workshop

    • Dates in the report grid, in both Live Preview and Run Full Report, now show as 07/01/2026 instead of a long date-and-time code.
    • The "Filter this report" window is wider, so long names such as payer names are no longer cut off.
    • Pick-from-list boxes show more items at once. A line under the list shows how many items you have picked and names them, with a reminder to hold Ctrl (Cmd on a Mac) while clicking to pick more than one.
  22. Vigil Released Services from the KIS desktop system · Service Search and the client Services list · Staff dashboard · Service page · Payments and write-offs

    Services from the KIS desktop system

    • Services entered in the KIS desktop system now show the right status everywhere in Vigil. A service that has been posted shows as Complete, and one that has not been posted yet shows as Pending. Before, the same service could show as Draft, Pending or just "P" depending on the screen.
    • Nothing about your desktop records was changed - only how Vigil shows them.

    Service Search and the client Services list

    • The Complete filter now finds posted services from the desktop system.
    • Two new Status filter options: "Posted" and "Pending (legacy)".
    • The Services tab on the client page now shows posted services as posted instead of Pending.
    • The client dashboard shows clear Posted and Pending badges.

    Staff dashboard

    • Services from the desktop system no longer appear under signatures pending or "needs supervisor signature". They never needed a Vigil signature.

    Service page

    • Services from the desktop system no longer show the signing step tracker or a void-signature option.
    • The status badge no longer flashes "Draft" while the page loads.
    • Services authorized through a treatment plan no longer show as Draft.

    Payments and write-offs

    • Posting a payment file (835 remittance) or writing off a balance no longer changes whether a service shows as posted or complete. Payment status is shown on the claim instead (Paid or Partial), and a partly paid service stays complete.
  23. Vigil Released Navigation · Client chart · Phones and tablets · A seasonal touch for October

    Navigation

    • The top navigation bar now stays at the top of the screen on every page while you scroll. A soft shadow appears under it once the page scrolls beneath it.
    • On the Schedule, Staff, Underwriter's Desk and My Reports screens, headers and panels that stay in view while you scroll now sit neatly below the navigation bar.

    Client chart

    • Once you scroll past the client's header, a slim bar slides in under the navigation bar with the client's photo (or initials), name, MRN, gender and age, status and the Add Service button - so you always know whose chart you are in. Click the name to jump back to the top.
    • The section menu on the left now stays in view while you scroll.

    Phones and tablets

    • Vigil now fits phones and small tablets. Pages lay out for the size of your screen instead of showing a shrunken desktop page.
    • Typing in a field on an iPhone no longer zooms the whole page in.
    • Buttons that used to appear only when you hovered with a mouse - the Demographics edit pencil, the medication row buttons and the program remove button - are now always visible on touchscreens.
    • Wide tables can be swiped sideways on a phone.
    • Larger windows such as Add Service, Billing Record, Add Client, Admission, Diagnosis and Treatment Plan open full-screen on phones.
    • Small icon buttons are larger and easier to tap.
    • Your Kindled companion now steps aside while a window is open, so it never covers a Save or Next button, and it is smaller on phones.
    • On the Schedule, the month bar swipes sideways on phones and keeps the current month in view.
    • The phone menu no longer shows an empty gap under "Services".

    A seasonal touch for October

    • Throughout October, the numbered step circles in Vigil's step-by-step windows (Add Service, Add Client, payer setup, Appointments and the program wizard) become pumpkins, as do the circles in the Treatment Plan signing steps and the Service Entry signing progress bar.
    • Steps you have not reached yet are pale pumpkins, the step you are on is a ripe orange pumpkin with a soft candle-like glow, and finished steps are deep orange. Step numbers, checkmarks and icons still show.
    • Nothing about how these windows work has changed. The pumpkins switch off on their own on November 1. If your computer is set to reduce motion, the glow is left off.
    • This is the first of more seasonal touches to come.
  24. Vigil Released Service Search · Service entry · Underwriter's Desk (Config > The Underwriter's Desk) · Billing Center · Eligibility · Reports Workshop · …

    Service Search

    • A new "Service ID" column is now the first column. You can sort by it, and clicking an ID opens the service.
    • A new "Service ID(s)" filter finds services by ID. Type or paste one or many IDs separated by commas or spaces, or paste a column straight from Excel. A note under the box tells you which IDs were not found, which entries were not numbers, and how many matches your other filters are hiding.
    • Choosing "Billed" in the Status filter now works. The same fix applies to the Services list on the client page.
    • The Export button now works. It downloads a spreadsheet (CSV) of every service matching your current filters and sort - not just the page on screen - up to 25,000 services. A larger search asks you to narrow it first.

    Service entry

    • The client's name and MRN now link straight to the client's face sheet.
    • The Billing card now shows who the service is billed to in a highlighted "Billed to" block. It is shown to everyone, including read-only users and on services whose payer cannot be changed.
    • Services entered in the legacy system now carry a "Legacy" tag, visible even when the Billing card is collapsed, with a short note that their units and charge stay as the legacy system recorded them.

    Underwriter's Desk (Config > The Underwriter's Desk)

    • Payer Directory: if your site has not added any payers yet, you now see your payment categories and a "No payers yet" note instead of an empty "Nothing matches" page.
    • 837 Routing: adding a routing now asks for the EDI Payer Name printed on claims, filled in for you from the routing name. Claim filing indicators and clearinghouse ID qualifiers you saved earlier are now kept and shown when you reopen and save a routing.
    • A payer address is now required only when you fill one in (and always for ODMS). Routings without an address can build claim files again.
    • Payers, routings and payment categories still in use on active client billing records can no longer be hidden by accident from any screen. You are told what to move first.
    • Organization: the separate "Contact Phone" box is gone - claim files use your organization Phone, and the live preview shows exactly what is sent. The completeness badge now includes Tax ID. Entries that are too long get a clear message instead of an error.

    Billing Center

    • Validation now flags claims whose EDI Payer ID is longer than 10 characters, so they are not sent cut short.
    • Bills whose routing does not match the client's billing record now show a warning to check before batching.
    • The "Organization" fix button on a ZIP code message now opens the right tab.

    Eligibility

    • If your organization name is blank, eligibility checks now ask you to add it instead of using another name.

    Reports Workshop

    • "Service Staff ID" is now available on the Billing and SAMH Funding report subjects.

    Client dashboard

    • On the Care Team card, the primary-staff star no longer overlaps long staff names.

    Glimmers

    • Items bought in the shop now appear on your companion. Forming a new companion now sets it up completely, the shop checks for your companion before spending any Sparks, and opening the Hearth fixes an affected companion automatically. We will restore everyone's purchased items during the update at your site - no purchases were lost and there is nothing you need to do.
  25. Vigil · Database update Released Lookup settings now survive updates

    Lookup settings now survive updates

    • Settings your agency changes on built-in lookup items are now kept when your system is updated: which FASAMS fund codes are reported to the state, any built-in item you have hidden, and the program manager on placement types. Before, each update quietly put these back to their defaults. After this update, re-check your FASAMS fund code switches once (Underwriter's Desk, Payer Directory) - from then on they will stay as you set them.
  26. Vigil Released Service pricing and billing · Sliding fees · Changing a bill's payer · Billing Center · Eligibility · Fixes

    Service pricing and billing

    • Services are now priced consistently no matter where they are entered (service entry, group sessions, bed days, treatment plans). Time-based services bill by unit, with partial units rounded up, and claims now carry the correct number of units.
    • Each payer can now be set to allow or not allow sliding-fee discounts.
    • A service can only be billed to a payer listed on that service's "Payers Allowed" list.
    • Claims now check that the client's billing record covers the date of service.

    Sliding fees

    • Sliding-fee discounts now use the family income and household size from the client's FASAMS outcome form (POMS). The screen shows which form and date the income came from.
    • Clients just above a tier's limit now receive the next tier instead of the full rate.
    • Every discounted amount is labelled "sliding fee price".
    • The sliding-fee scale editor now points out tier setup problems.

    Changing a bill's payer

    • A new "Bill a different payer" button on a service's billing section lets you move the bill to another of the client's payers, for services entered in either system.
    • Moving a bill updates its routing. A bill in a draft batch is taken out of the batch; a bill already built or submitted cannot be moved, and the screen explains why.

    Billing Center

    • Validating selected claims no longer fails on claims with many errors.
    • "Return to Clinical" now works from the reassign screen.
    • The Ready to Bill list shows billed units.
    • 837 files now use the batch's own routing, so the whole file goes to the correct clearinghouse.

    Eligibility

    • When a payer's eligibility response says coverage is inactive and gives an end date, that date is now recorded on the client's billing record. Any record that already had a different end date is listed in the results summary for review.

    Fixes

    • Signed services now correctly show as signed when reopened.
    • Group sessions can now be signed, and the screen names any attendee who was skipped and why.
    • Bed-day posting now completes and creates bills.
    • Emergency contact relationships are no longer cleared when saving Demographics.
    • Display clean-ups in the Billing Center, Service Entry and sliding-fee screens.

Talk to the people who built it.

No sales team, no ticket queue. Tell us what's hurting and you'll hear back from Rodney.

Email Rodney→Call 843 319 8444