Platform architecture

One linear chain, every feature in order

Each stage inherits verified data from the stage before it. The integrity of the final payment depends on the integrity of every step that preceded it. That is why the features are presented in the order they operate, not in order of importance.

  • Features 1-2 · foundational reference layers
  • Features 3-7 · entitlement and prospective control
  • Features 8-12 · processing, settlement and insight
Everything in one chain

Four control points. One continuous record of liability.

From the moment a member presents to the moment a provider is settled, MedicalBytes keeps every record, rule and receipt in one place, and every decision inherits verified data from the step before it.

01

Prove the person

Fingerprint or face verification at the front desk, matched against the enrolled member register.

  • Sub-second one-to-one matching
  • Liveness and anti-spoofing checks
  • Offline capture with deferred sync
02

Decide before treatment

Cover, clinical appropriateness and affordability settled up front, automatically where the rules allow.

  • Live benefit and sub-limit balance
  • Straight-through auto-authorisation
  • Clinical review only where it adds value
03

Read any invoice

Paper, PDF, photograph or electronic feed converted into clean, coded, validated structured data.

  • OCR with per-provider layout training
  • ICD-10 and CPT coding applied
  • Duplicate line and invoice detection
04

Pay what is due

The full rulebook applied per line, then a reconciled payment run with approval ceilings enforced.

  • Line-level adjudication and audit
  • Segregation of duties on every run
  • Remittances and provider statements
Platform architecture

The platform features

The sequence matters. The architecture is deliberately linear: each stage inherits verified data from the stage before it, and the integrity of the final payment depends on the integrity of every step that preceded it. Tap a feature to open it.

Foundation · security & governance

Role based access control

Permissions attach to roles, not people. A user inherits exactly the rights of the roles held, scoped to the schemes, clients, branches and providers they may act on, for screen visibility and transaction authority alike.

Business value · protects clinical and financial data, blocks internal collusion, and gives audit examinable evidence.

  • Granular module and action rights: view, create, edit, approve, reverse, export
  • Segregation of duties enforced: the maker cannot be the checker or the payer
  • Approval hierarchies with monetary ceilings per role and per user
  • MFA, SSO, session and device controls, plus temporary elevation that expires by itself
  • Diagnosis and identifier masking for users without a clinical need to know
  • Immutable audit trail of every login, override and record change, before and after

Features 1 and 2 are foundational reference layers · 3 to 7 govern entitlement and prospective control · 8 to 11 govern processing and settlement · 12 closes the loop.

Walk the chain

Follow one claim, from front desk to bank file

Click through the five control points the platform applies to a single encounter. Every step inherits what the step before it verified. That is exactly why the last number can be trusted.

The encounter

Illustrative walkthrough using sample data.

Feature 04 · Biometric identification

Prove the person, then trust the claim

The member places a finger on the reader at reception. The template is matched one-to-one against the enrolled record, liveness is checked, and the encounter is stamped with member, facility and time before anything clinical happens.

MemberP00-000000-M0001
VerificationFingerprint matched · 0.4s
FacilityBryanston Gate · Tier 2
EncounterStamped & non-repudiable
MedicalBytes point-of-service verification screen

Point-of-service app

Walk your own claims through the chain

Bring a sample of real claims and we will show you what the engine does with them, line by line.

Processing

From any invoice to a reconciled payment

Three engines do the work that normally consumes a claims floor, and each one hands the next one data it has already validated.

01

AI powered invoice reception

Invoices and clinical documents in any format (paper, PDF, photograph or electronic feed) read into clean structured data. No manual keying, no transcription risk.

  • ✓ Provider-specific layout training
  • ✓ Confidence scoring and validation queue
  • ✓ Source image archived against every claim
02

ICD-10 & CPT coding engine

Authoritative clinical coding, so the diagnosis, the billed activity and the contracted tariff always speak the same language.

  • ✓ Diagnosis-to-procedure consistency checks
  • ✓ Unbundling and up-coding detection
  • ✓ Code bound to the tariff in force on the date
03

Automated payment runs

Adjudicated claims turned into accurate, reconciled payments, with approval ceilings and segregation of duties enforced by the platform.

  • ✓ Bank file generation and EFT integration
  • ✓ Remittance advice and provider statements
  • ✓ Ledger posting and line-level reconciliation

Tariff sets, scheme rules and provider contract terms are loaded per client, so the engine adjudicates against your rulebook rather than a generic one.

Walk your own claims

Bring a sample. We will show you the chain.

Give us a set of real claims and we will run them through the engine line by line: identity, entitlement, authorisation, coding, adjudication and settlement.