GA USABook a call ↗

Nomalix Lab

Find the gap
Make the next move

Glucose result sent
Patient ID missing
Result still not seen
Found in secondsRun the scan ↓

How a gap gets closed

  1. Assess the gap

    EHR · Dynamics 365 · REDCap · HL7 v2

  2. Map the meaning

    FHIR · USCDI · LOINC · SNOMED CT

  3. Build & validate

    Profiles · terminology · synthetic patients

  4. Hand off

    Dashboards · SOPs · training

Patient data exchangeInteractive workflow

Hands-on engineering

Health records move between systems all day. When one arrives broken, most systems pass it along anyway, and nobody notices until a patient’s result goes missing.

Start with the mapping tool: it lines up each source field with the standard it should match. Then the backend validator checks every record at a gate. A broken one is held and explained instead of being sent, then released once it is fixed.

Try it: in the mapping tool, pick a field and review its mapping. In the validator, choose a scenario and press Trace record.

Illustrative physician in a white coat looking toward the Scan workspace

Better information
for the next decision

NOMALIX SCAN / PRELIMINARY STRUCTURAL INSPECTIONBROWSER LOCAL
TECHNICAL FINDINGS
Your record’s path starts here.
Load the example or paste synthetic JSON to inspect its structure.
Run this on your own systems ↗

Agent workflow

Automation that waits for a person

Four small software agents share one job. The first reads an incoming record. The second suggests how to map its codes to a standard. The third checks that suggestion. The fourth makes sure nothing changes until a person approves it.

Every step is written to an audit trail, so you can see who did what and why.

Try it: pick a task, press Run agent workflow, then click any agent to see its role and what it is allowed to do.

The outcome: faster integration work, with a person still answering for every change.

NOMALIX / AGENT ORCHESTRATIONLOCAL PROTOTYPE · MODELS DISCONNECTED
INSPECT AN AGENT

A visible chain of responsibility.

Select an agent to inspect its role and permissions, or run the synthetic task to watch the handoffs.

TOOL CALLS / AUDIT TRAIL
  1. Awaiting a synthetic task.

Orchestration prototype: simulated agents, real browser-local tools, no language model or external endpoint connected.

Mobile workflow

Approve a fix from your phone

Not every reviewer sits at a desk. This is the phone view a care coordinator would use: see which record needs attention, check the fix NOMALIX proposes, then approve the hand-off.

Try it: tap the three screens below in order.

9:41●●● ▰
✳ NOMALIX OPERATIONS
CONNECTED CARE / DEMO

Exchange queue

See what needs attention.

Needs reviewSynthetic record NMX-014
↳
Patient exchangeNMX-014 · destination identifier
Held
✓
Lab resultNMX-012 · sample result
Ready
✓
Care referralNMX-011 · sample referral
Ready
Source→Map→Care
Local prototype. No patient data.
⌘Queue◇Rules↗Activity
9:41●●● ▰
✳ NOMALIX RESOURCE
INSPECT & MAP

Review the record.

Patient / synthetic-014

{ }
Source referenceDEMO-014
resourceTypePatient
identifier.valueMissing
The receiving system requires an exchange identifier.
Prototype mapping rule. Human review follows.
⌘Queue◇Resource↗Activity
9:41●●● ▰
✳ NOMALIX REVIEW
APPROVAL GATE

Review the hand-off.

Inspect before the next action.

◇

Awaiting a proposal

Prepare the identifier mapping on the middle screen to continue.

JSON parsingPassed
Identifier contractPending
Human approvalRequired
⌘Queue◇Rules↗Review