Book a call

Choose who to talk to

Pick who you’d like to speak with and book a time that works for you.

Dima Blyshchyk, CEO & Founder at Mitrix

Dima Blyshchyk

CEO & Founder

Max Fedaraka, Head of Business Development at Mitrix

Max Fedaraka

Head of Business Development

Industries / Healthcare / HIPAA-aware

HIPAA-aware software without the theater.

HIPAA-aware development means building controls into the product from the first sprint. We work inside your business associate agreements, role-based access model, and audit requirements, then document what we built so your compliance team can review it. We do not claim HIPAA, HITRUST, ISO, or SOC 2 certification. We support the review your organization runs.

BAA reviewRole-based accessAudit trailsRelease gates
Control review
Access modelRole-based
Audit trailEvent logged
RetentionPolicy set
Vendor reviewIn progress
BAAsigned before build
BAAsigned before build
RBACleast privilege by default
Auditevents recorded and traceable
Retainpolicy set per record
01 — Capabilities6 connected areas

What we build.

One workflow can touch a referral, a supplier, a delivery team, a patient, a payer and an EMR. We work across the chain, or just the handoff that hurts.

01

Business associate agreements

Work starts with a signed BAA and a written scope of the data we touch. We list subprocessors, name who can access what, and document the boundaries in the project plan. When scope changes, the agreement and the plan change with it.

BAAScopeSubprocessors
02

Role-based access and least privilege

Every role gets the smallest set of permissions that lets the job work. We define roles with your clinical and operations leads, test them against real tasks, and review them as staff change. Access reviews become a scheduled task with an owner.

RBACLeast privilegeAccess reviews
03

Break-glass workflows

Emergency access should open quickly and leave a clear trail. We build break-glass paths for the roles that need them, require a reason at the moment of use, alert the right people, and send every use into review. The path stays fast while the record stays honest.

Emergency accessReason codesReview
04

Encryption and environment separation

Data moves over TLS and sits encrypted at rest. Production, staging, and test environments stay separate, and test systems use de-identified or synthetic records. We document where keys live, who can rotate them, and how backups are protected.

TLSEncryption at restEnvironments
05

Audit trails and retention

We record who viewed, changed, or exported a record, with time, role, and reason where the workflow asks for one. Retention rules are written per record type and run as scheduled jobs. Logs are queryable, so your team can answer a review question without asking engineering.

Audit loggingRetention rulesEvidence
06

Release gates and vendor review

Each release passes a checklist that covers access changes, logging, data handling, and dependencies. New vendors get reviewed before they touch PHI, with a BAA where needed. Findings go into the backlog with an owner and a date.

Release gatesVendor reviewChecklists
02 — WorkflowEnd to end

The workflow we cover.

Every step is a handoff. The software has to keep the state, the reason and the evidence together, or operations rebuilds the process in spreadsheets.

01

Scope the data

Name the PHI the system will store, process, or pass through, and write down what stays out of scope.

Data map · Scope
02

Map roles and access

List every role that touches the system, then cut each one down to the permissions the work actually needs.

Roles · Permissions
03

Design the controls

Agree on break-glass rules, audit events, retention windows, and encryption choices before build starts.

Controls · Design
04

Build with logging on

Instrument the product as we build so access and change events land in the audit trail from the first sprint.

Build · Audit events
05

Review vendors and data flows

Check every third party that touches PHI, confirm agreements, and record the decision in the vendor register.

Vendors · Data flows
06

Gate the release

Run the checklist, fix what fails, and hand your compliance team the evidence they need for review.

Release gate · Evidence
03 — Where it breaksFour failure points

Where HIPAA-aware builds slip

Most problems show up after launch, when a new feature, a new hire, or a new vendor stretches controls that were designed for a smaller system. The fixes are usually simple to describe and slow to retrofit, which is why we plan for them at the start.

01

Access grows past the model

A role gets copied for a contractor, then another for a launch, and least privilege quietly becomes everyone can see everything. Access reviews catch it only if someone owns them and runs them on a schedule.

02

Audit logs nobody reads

Logs fill up, but no one can answer a reviewer question without an engineer poking at raw tables. Useful audit trails are designed around the questions a compliance team actually asks.

03

Retention with no owner

Records pile up because nobody decided how long each type should live. Setting retention per record type, then automating deletion and holds, keeps storage and review risk from growing quietly.

04

Vendors added after review

A team signs up for a new tool, sends it patient data, and tells no one. A vendor register and a short review step before any PHI leaves your systems prevent most of this.

04 — ModulesShipped or scoped per workflow

What the build is made of.

Modules follow the workflow, not a product catalogue. Each one gets an owner, an integration boundary and a way to reconcile with the system of record.

01Access control

Roles, permissions, and least privilege checks for staff, contractors, and service accounts.

02Audit pipeline

Event capture, storage, and search for views, edits, exports, and break-glass use.

03Break-glass flow

Emergency access with a reason prompt, alerts, and a review queue.

04Encryption layer

TLS in transit, encryption at rest, and a documented key rotation process.

05Retention jobs

Per-record retention rules, scheduled deletion, and legal holds with a named owner.

06Vendor register

A running list of subprocessors, their agreements, and review dates.

05 — EvidencePublic proof

What it produced.

Representative healthcare work. Client names are under NDA; the workflows and numbers are what we can share.

01

Healthcare software hub

Our healthcare practice covers software for providers, payers, and device teams, including patient portals, CRM, document AI, and business intelligence. Start here for the wider view of how we handle clinical data and regulated workflows.

Healthcare hub
02

EMR integration

We connect products to EHRs through HL7 interfaces, flat files, and APIs, with reconciliation work that keeps records aligned. Integration projects are where access rules and audit trails meet the data your clinical teams rely on.

EMR integration
03

Healthcare document AI

Document extraction and retrieval pipelines handle records with PHI, so the same controls apply: scoped access, review steps, and audit events. The page covers how we keep humans in the loop on extracted clinical content.

Document AI
06 — ApproachBuild, buy or extend

Build internally or bring a partner

Teams often have the domain knowledge and not the compliance engineering time. We can work alongside an internal team, take a defined scope, or review what you already built. The decision usually comes down to how much control you want during the build and how much documentation you can produce afterward.

01

Internal team keeps product knowledge and hires us for controls, review, and release gates.

02

Partner build suits a defined module with a fixed review window and an agreed evidence pack.

03

A controls review works when the product exists and you need gaps found before an audit.

04

Handover includes runbooks, access maps, and the audit queries your team will need.

07 — StackChosen per constraint

What we build it with.

Existing platforms respected, new surfaces kept boring. The stack follows the integration and compliance constraints.

TypeScriptPythonReactNode.jsPostgreSQLAWSAzureDockerKubernetesTerraform
Platforms and systems
WebiOSAndroidDesktopCloudOn-premiseREST APIsHL7 and FHIR
08 — FAQShort answers

Questions buyers ask.

If yours is not here, send it. We answer in plain language, with the constraints we would check first.

Are you HIPAA certified?

No. Mitrix does not claim HIPAA, HITRUST, ISO, or SOC 2 certification. HIPAA does not have a formal certification for software vendors. What we do is build inside written controls, sign a BAA, keep the documentation, and support the compliance review your organization runs with its own counsel and auditors.

Will you sign a business associate agreement?

Yes. A signed BAA is in place before build work starts. We scope the data we handle, list subprocessors, and update the agreement when scope changes. If your legal team has its own template, we review it early so contract questions do not stall the first sprint.

Can PHI go into AI features?

Only when you decide it can and the controls support it. We prefer de-identified data for development and testing, and we route extracted or generated content through human review before it reaches a record. Vendor terms, data retention, and model providers are reviewed before any PHI is sent.

What does the audit trail need to capture?

At minimum, who accessed a record, when, from where, and what they did. Workflows that need a stated reason should capture one. Exports and break-glass use need their own events. We design the schema around the questions your reviewers ask, then test that the answers come back without engineering help.

What does a HIPAA-aware build cost?

It depends on scope, integration count, and how much documentation your review needs. Controls work adds effort to design, logging, and testing, and that effort is easier to estimate once the data flows are mapped. We quote a defined scope after a short discovery rather than a per-hour guess.

How long does it take?

A focused controls pass on an existing product usually runs a few weeks. A new module with integrations and review takes longer, and we plan it in stages so your team sees working software early. The release gate is the last step, and it depends on how quickly findings get fixed.

Bring us the workflow that hurts.

Tell us where the handoff breaks: intake, eligibility, delivery, reconciliation, billing or the patient experience.