Got Questions?
Here Are Straight Answers

You do. Opexia is an engineering partner, not a SaaS vendor: on final payment you own the source code, data, and intellectual property, and we don't charge per-seat or monthly licensing fees for software we build for you.

EHR integration is work we scope carefully rather than a track record we claim. We design integrations against HL7 v2, FHIR R4, and each vendor's published APIs, and access timelines depend on the vendor's own developer program. We'll cover what's realistic for your EHR on the first call.

Robotic Process Automation (RPA) uses software bots to handle repetitive, rules-based tasks, such as logging into payer portals to check claim status and writing the results back to your practice-management system instead of re-keying them by hand. Where a payer offers an API or EDI transaction, that is usually more reliable than a bot, so we use that route first. We automate a payer portal only where the payer's terms of use allow it or the payer has approved it in writing, and we do not work around CAPTCHA, bot detection or two-factor login.

No engineer can honestly guarantee an audit outcome. What we do is build the controls security reviewers look for from day one (encryption, audit logging, role-based access, and least-privilege access to infrastructure) and document them so your team can answer security questionnaires with evidence.

Typically a few months; scoped after discovery. The main variables are how many workflows the first release covers and whether it depends on third-party approvals, such as an EHR vendor's developer program.

Yes. Software needs ongoing iteration and security patching. We offer maintenance, security updates, and feature work after launch, with the scope and response times agreed per project.

HIPAA compliance and SOC 2 describe an organization's whole program, not a codebase, so we don't label software as compliant. The platforms we build are built to HIPAA requirements (encryption, audit logging, role-based access), which gives your compliance program a solid technical foundation. We sign a Business Associate Agreement (BAA) before any PHI access: no one on our team sees protected health information until it is executed. SOC 2 is an attestation report issued by a licensed CPA firm under AICPA standards; Opexia holds no SOC 2 report of its own. We can build the technical controls it examines, but the audit itself is between your organization and the auditor.