Dashboard

Live overview across Document Vault, Cleansing, Operations, SOPs and users. Auto-refreshes every 20s.

—
Loading dashboard…

Uploads

Load one or more PDFs. Extraction runs page-by-page in your browser, then the Flask backend applies your rules.

Drop PDFs or a folder of PDFs here

Files picks individual PDFs · Folder pulls every PDF inside (recursive). Drag-and-drop supports both.

No files uploaded yet

Drop PDFs above or click Browse to get started.

Testing / maintenance Duplicate index: —

Results

One row per patient. Click View to open that patient in Views.

Patients
0
No data
Files processed
0
—
Facilities
0
—
Physicians
0
—

No extracted data yet

Upload PDFs and run processing from the Uploads tab.

Views

Open a patient from Results to see Form, HTML, PDF, and JSON representations in one place.

No patient loaded yet

On the Results tab, click View on any row to open that patient here.

Extraction rules

Edit per-patient extraction rules. Rules are persisted on the backend.

Each rule runs once per patient block. between grabs text from start to end. regex uses a regex with group / flags. fallbackEnd is an optional list of alternative end markers.

Settings

Global archive toggle and SFTP destinations. Admin sign-in required to change.

Archive

When on, the original PDF and its index (patient list + page ranges) are pushed to every enabled SFTP site after processing. Turn off during testing.

SFTP destinations

Index orphan PDFs

Find PDFs on pull-mode SFTP sites that aren't indexed in MongoDB yet, pull each one through the browser, run the same extraction pipeline as manual uploads, and push the resulting index back to the same site.

RCM Inferences (Claude)

Configuration for the RCM Inferences button in the Form View (next to Medical Conditions). Ports the Medicare Billing Analyzer's prompt to Claude and returns Claim Routing & Bundling, Part B Rationale, and Part A Rationale. API keys are stored on the server in data/rcm_settings.json.

Edits take effect on the next RCM Inferences click.
Upload & queue
STEP 01 — Stage Excel workbooks for merging
MARTAR looks for these sheets inside each workbook: scrub, recon, validate, code, bill. Choose which stages to combine below — skipping unwanted stages makes the merge faster. The combined output always includes two leading columns: Record Type (source file) and Record Stage (sheet it came from).

Upload files

.XLSX / .XLS

Select one or more Excel workbooks individually. Drag & drop works too.

Upload folder

DIRECTORY

Pick an entire folder — all Excel files inside will be loaded at once.

PROCESSING Loading 0 / 0 files (0%)
MERGING Merging 0 / 0 files (0%)
Stages to include
#File nameSheets matchedSize
No files queued — upload to begin
0 file(s) queued / 0 matching sheet(s)
Combined output
STEP 02 — Explore, filter, and export

Nothing merged yet

Upload at least one Excel file, then click Merge workbooks to see the combined output here.

Claim inferences
STEP 03 — Clean / Dirty / Blank claim analysis across Scrub, Code, Bill

No inferences yet

Upload and merge your workbooks (including at least scrub, code, and bill), then come back here to run the claim analysis.

Reports

Filter and export stored MongoDB data by client, facility, and date.

No results yet

Pick filters above and click Run report to query the MongoDB archive.

Reporting Engine

Drag fields onto the canvas to build any report. Save the layout as a template for reuse.

Filters Limit which rows are included
Rows Group by (one row per combo)
Columns Pivot into columns
Values (measures) SUM, COUNT, AVG, …
Drop fields onto the zones above to start.

EDI Analyzer · Upload 837

Drop one or more 837 files (Institutional focus). The parser, validator, and analysis engine run on the backend. ANSI X12 005010X223A2.

Drag & drop 837 files here

or

Accepted extensions: .837 .txt .edi .dat .x12 — also pasted text bodies.

EDI Analyzer · 837 Analysis

File-level analysis dashboard. Pick a file to drill in.

Upload an 837 file to see analysis here.

EDI Analyzer · 837 Inferences

Cross-file aggregation across every uploaded 837. Dollar totals, payer mix, filing breakdown, monthly trend.

Loading inferences…

EDI Analyzer · Claim Browser

Search and filter every parsed 837 claim. Click a row for the full claim detail.

Claim # Patient Payer TOB Stmt period Adm/Disch Principal Dx DRG Billing NPI Lines Charge Issues

No claims yet — upload an 837 file.

EDI Analyzer · Upload 835

Load Electronic Remittance Advice files. Once uploaded, match them against your 837 claims on the Payment Posting tab.

Drag & drop 835 (ERA) files

or

EDI Analyzer · Payment Posting

Match 835 payments to stored 837 claims, review billed / allowed / paid, then post to the audit trail.

Run match to see candidates.
Patient ctrl # Patient Payer claim # Stmt period Billed Paid Pt resp Adj Status Match

Recent postings

Posted at Claim # Patient Billed Paid Pt resp Match

EDI Analyzer · Validation Rules

Enable / disable rules and adjust severity. Changes apply to every re-validation, but not to already-stored analysis summaries.

Required segments

Format checks

Code-list checks

Balancing

Standard Operating Procedures

Browse the SOP index, open attached documents in the viewer, and upload supporting files (PDF, DOCX, XLSX, images, TXT) to any entry.

— entries
SOP code Title Owner Action Files Source Actions
Loading…

Add SOP entry

Create a manual SOP entry. The next default code is suggested (SOP.M-N); override it if your team uses its own numbering. Attach files afterwards from the Browse view.

SOPs · Seed & admin

The seed Excel lives in the database. Replace it when your index workbook changes, then re-seed to upsert. Manual entries and uploaded attachments are preserved unless you explicitly purge them.

Seed file

Loading…
Download cached seed

Statistics

—

Purge

Each button asks for confirmation before deleting.

Document Vault

Pick an organization at the top to see its filed documents. Narrow further by facility, category, or month.

Pick an organization to see its documents, or leave blank for all.
0 documents
Document Organization Facility Category Patient Month Size Uploaded Actions
Loading…

Upload to Document Vault

File one or more documents against an organization, facility, category, and month. Files stream to MongoDB (GridFS).

Facility legal name is for reporting only.
User-facing site — used in the SFTP folder path.
PDFs, images, and Office docs are all accepted (up to 1 GB per request).

Dictionaries

Add and remove the entities used to file documents. Deleting an organization or facility also deletes every document under it. Deleting a category only removes it from the picker — historical documents keep their tag.

Organizations

    Facilities

      Keywords —

        Categories

          Cleansing · Billing Workflow patients

          Filter uploaded Billing Workflow documents by organization, facility, and month. The app parses every matching workbook, groups rows by patient identifier, and shows one compact card per patient — steady values as text, varying values as dropdowns.

          Patient Lookup

          Search the persisted patient store by Patient ID, name or physician. Every patient that reaches the Cleansing stage is saved to the database with its coding & billing status.

          Enter a Patient ID (or name) and press Search.

          Operations · Coding

          Fetch one claim at a time from the Cleansing pool. Each fetch assigns a single patient claim to you. Fill the Medical Coding section, then set the status to Move to Billing to hand it to the Billing team.

          No claims assigned yet. Pick a scope and press Fetch next claim.

          Operations · Billing

          Auto-fetch claims that coders have moved to billing. You only see claims assigned to you. Fill the Billing section for each.

          No billing claims assigned yet. Press Fetch next claim.

          Users

          Every account with access to the app. Admins see all modules implicitly. Assign specific modules to non-admin users so they only see what they need.

          Email Name Role Modules Organizations Last login Actions
          Loading…

          Add user

          Create an account and grant module access. The user can sign in with the email + password below immediately.

          Access
          Modules Sections this user can open
          Organizations Whose data they can see

          Settings · SFTP destinations

          Uploads to the Document Vault are auto-pushed to every enabled destination flagged as Vault target. Files land under <prefix>/<org>/<sub-facility>/<YYYY-MM>/<category>/<filename> — missing folders (including new months) are created on the fly.

          Name Host · user Path prefix Status Auto-push Vault Actions
          Loading…
          Filter