Docs · How PXNT works
Products
MDXT, BBGI and ECPK are products. Each brings its look, its words and its own parts, and runs on what PXNT builds once.
The three products
| Product | For | Runs on |
|---|---|---|
| MDXT | Care teams | the platform and AVGVSTVS |
| BBGI | Operations across many sites, worldwide | the platform and AVGVSTVS |
| ECPK | Service networks between organizations, customers and providers | the platform and MERCVRIVS |
A product is a configuration
A product brings what is its own and nothing else:
- its look: colours, fonts, corners;
- its words, in its languages;
- its own parts, such as MDXT's care records or BBGI's site panels, placed in the slots the shared screens leave for them;
- which shared parts it switches on;
- its own database and where it runs.
Shared code never asks which product it is running in. A difference is a setting.
One operations app
MDXT and BBGI do the same kind of work: who works where, tasks step by step, risk, problems, handover. So they will run the same screens, each in its own look. Each screen is taken from whichever product does it better: Command and the schedule from BBGI, the worker's cockpit, opening a record and signatures from MDXT.
Switching, a part at a time
A product changes over one finished part at a time, once that part runs in both products' settings on a test copy. Nothing in a product changes before that.