340B programs, run in one place.
MedMatrix Rx administers 340B pharmacy programs for hospitals and their participating specialty practices.
A 340B program is judged on its records
Who is credentialed and screened, which drugs the formulary covers, what the agreements say, how each month settles, and what an auditor will ask to see. MedMatrix keeps them in one system, in four areas that read from the same records.
Credentialing on the three-year clock, OIG exclusion screening, and privileging packets for the covered entity.
- The provider roster, with each credential’s status, where it came from, and the three-year re-credentialing clock.
- OIG exclusion screening of providers, staff and vendors on a cadence, with the evidence kept.
- Privileging packets assembled for the covered entity, and the decision it makes recorded.
The conforming-drug list with its effective dates, the agreements behind it, and OPAIS registration.
- The covered entity’s conforming-drug list, with effective dates.
- Covered-entity and network participation agreements, with their terms and renewal dates.
- OPAIS registration and recertification status for each covered entity.
Each month reconciled: collections, drug cost and fees, and the inventory to replenish at each site.
- Each month goes from draft to reconciled to settled, with collections, drug cost and fees accounted for.
- The inventory position at each site, replenishment purchases and their discrepancies.
- What dispenses accumulate, drug by drug.
The compliance control library, an audit workspace, and the training records of the staff.
- A library of compliance controls, each reviewed on its own cadence.
- An audit workspace for self-audits and what they find.
- Training courses assigned by role, with due dates and completions.
The 340B engine, underneath
Covered entities and their sites, drugs matched to NDCs with pricing and substitutability, and the checks that place or hold an order. All four areas read from it.
Every order is checked before it is filled
Each prescription becomes a pharmacy order, and the 340B engine places it or holds it and says why.
The prescription becomes an order
Each prescription becomes a pharmacy order for a drug, by its NDC, and nothing is filled until it is checked.
The 340B engine checks it
Three things: the patient is on the eligible list, the NDC is on the formulary, and the NDC is one it recognises.
Placed, or held with the reason
A held order says why. Once the roster or the formulary changes, one click checks it again, and the answer is written on the order.
Records you can stand behind
A program’s records are only worth what an auditor can rely on. These are the rules they are kept under.
- Patient data stays in the engine
- Patient details are withheld unless three things hold: a business associate agreement on file, the covered entity’s own opt-in, and access granted to the reader by name.
- Every change leaves a trail
- Sign-ins and changes are written to an audit trail. The service ledger is sealed into packages, and anything added after a seal shows as not yet sealed.
- Each customer sees only its own
- A customer’s accounts are bound to its covered entity and see only its records, and the database’s row-level security keeps each organization’s data apart beneath the screens.
Who we work for
Covered entities
Hospitals and health centers in the 340B program: their providers, formulary, agreements, registration and monthly settlements.
Specialty practices
The practices that take part in a covered entity’s program: their participation agreements, medical-director PSAs, provider fees, and a formulary of their own to search.
Contract pharmacies
The pharmacies that fill for a program: orders placed or held with the reason, and the inventory to replenish at each site.
Questions and answers
Who is MedMatrix Rx for?
Covered entities in the 340B program, the specialty practices that take part in their programs, and the contract pharmacies that fill for them.
Which parts of the platform work today?
All four areas: providers, formulary and agreements, settlements, and audits and training. Each is a working screen today, and all four read from the same records underneath.
Can I create an account?
No. There is no public sign-up. An administrator makes an account for each person who works in a program we administer, and they sign in with it.
Where is patient data kept, and who can see it?
In the 340B engine. Patient details are withheld unless three things hold: a business associate agreement on file, the covered entity’s own opt-in, and access granted to the reader by name.
How do we start?
Contact us and tell us about your covered entity, the practices and pharmacies in it, and what you need kept in order.
Talk to us about your program
Tell us about your covered entity, the practices and pharmacies in it, and what you need kept in order.
Contact usWorking in a program we administer?
Sign in with the account an administrator made for you. There is no public sign-up.