18 September 2026

The modules of the system, and what each one does today

This is every part of the system, in the order we track it. The state word on each row is the state we hold in our own map today. Nothing on this page is rounded up.

There are 17 modules.

2 of them work today on the test system.

4 are part built.

9 do not exist yet.

2 are parked on purpose.

A module is only called working when it has been run from end to end and we can name the run. Both of the working ones were run with a test card. No family has paid real money through the system.

The four words

What each state word means

  • WORKS (UAT)

    It has been run from end to end on the test system, and we name the run.

    2 modules
  • PARTIAL

    Some of it is proven. The rest is named, and it is listed below.

    4 modules
  • NOT BUILT

    It does not exist yet, whatever the code may hold.

    9 modules
  • PARKED

    We chose to stop work on it for now. It is not lost and it is not started.

    2 modules

Module by module

All 17 modules, A to Q

  1. A WORKS (UAT)

    The family pays

    Module map row A. Take a payment.

    A family pays by card on the processor's own page, through our flow. We never hold the card number.

    Proof

    Run of 18 September 2026, this morning.

    TRX reference FB6ULVHDFKP8HK5.

    The test card was charged $7.85.

    Read back off TRX by that reference: approved.

  2. B WORKS (UAT)

    The mirror, which is the writeback and its mappings

    Module map row B. Write it back to Ortho2.

    The receipt lands in the practice's own ledger and closes the instalment. The front desk never leaves the software it already uses. This is the product.

    Proof

    Run of 18 September 2026, this morning.

    Ortho2 receipt 25239.

    The open count before the run was 24.

    The open count after the run was 23.

    That is a move of exactly one.

    The instalment's completed flag turned from false to true.

  3. C NOT BUILT

    Scheduling

    Module map row C. Scheduling and recurring.

    The job is to collect the later instalments with nobody clicking. It does not exist yet. The direction is to let TRX hold the plan and for our software to read each result and write each receipt back. Our loop has never run.

  4. D PARTIAL

    Install, update and shut down

    Module map row D. Install, update, uninstall.

    A clinic installs it and it survives a restart. The install passed on Windows 11. The same file passed on Windows 10 Pro. Update and uninstall are not tested, and it has not been put on a real practice machine.

  5. E NOT BUILT

    Licence and switch-off

    Module map row E. Licence and shut-off.

    A clinic that stops paying us stops taking payments, after it has been told. It does not exist yet. The rules are written down, including the grace period and the reminders that come first.

  6. F PARTIAL

    Watching it and raising the alarm

    Module map row F. Reliability and alerting.

    When the money moves and the receipt does not, a human has to find out. The alarm codes are right and the front desk band that shows them is written. No office has it yet, and it has not run on Windows. Two card-on-file alarms still have nothing reading them.

  7. G PARTIAL

    Boarding a clinic

    Module map row G. Onboarding a clinic.

    A new practice goes live by filling in a record, with nothing edited in code. One practice has a config. There is no production record for it yet. Two posting ids are still open. One of them is not ours to set.

  8. H PARTIAL

    Compliance and legal

    Module map row H. Compliance and legal.

    We can take a real family's money without exposing anyone. Our map calls this part built, and says some of it is not ours. A patient data agreement is drafted and it is not signed. A lawyer has to read it first. Three things that agreement needs from the product are not built.

  9. I NOT BUILT

    Our own TRX hierarchy

    Module map row I. Our own TRX hierarchy, our CRM.

    New clinics would sit under us at TRX, where we add them, see their sources and switch them on or off. Nothing of ours does this. We are working under somebody else's setup today. Setting up our own is an open item with TRX.

  10. J NOT BUILT

    A clinic signs up and pays us monthly

    Module map row J. Clinic signs up and pays monthly.

    A doctor clicks join, signs, pays and is set up. It does not exist yet. The one-time module fee has a design and the monthly billing has none. Who the clinic pays is still an open decision.

  11. K NOT BUILT

    The clinic admin screen

    Module map row K. Clinic admin console.

    One screen showing every clinic: what they owe, what we have sent them, and whether they are on or off. It does not exist yet. The 5 states it shows are already decided. It is the screen that drives the switch-off above.

  12. L PARKED

    Moving the existing book over

    Module map row L. Move the existing book off Global Payments.

    Families who already pay through the old processor move across without retyping a card. We parked this on purpose while the new customers come first. Keys for 8 locations have been sent. The step that hands them to the old processor has no owner.

  13. M PARKED

    Bank payments

    Module map row M. ACH.

    A family pays from a bank account instead of a card. We parked this on purpose to get cards working end to end first. A clinic would have to sign a bank payment agreement before it could be switched on.

  14. N NOT BUILT

    Practices on other systems

    Module map row N. Practices on other systems.

    Practices that run other chart software get the same bridge. It does not exist yet. The 3 dental offices named for it are waiting.

  15. O NOT BUILT

    TRX financing in our screens

    Module map row O. TRX consumer financing in our screens.

    A family applies for TRX financing at the front desk or on the pay page. Nothing of ours does this. TRX has said it is a focus for them right now.

  16. P NOT BUILT

    TRX agents sell it

    Module map row P. TRX agents sell it.

    A TRX agent sells a practice one package: our software, the card processing, and a terminal if the office needs one. Nothing of ours exists for it yet. TRX asked for a demo an agent can show, and we have not made one.

  17. Q NOT BUILT

    Boarding a clinic's TRX merchant account

    Module map row Q. Board a new clinic's TRX merchant account.

    A new clinic gets its TRX merchant account, its agreements and its payment page switched on. Nothing of ours does this. Today it takes emails to TRX staff and somebody chasing them.

Said once

What is not here yet

We cannot void a payment from inside Ortho2 today.

Scheduling is next.