FAQ.
Questions Aurora Link is asked most often, grouped by audience. If you do not find the answer you are looking for, the contact page is the fastest path to a direct response.
Jump to a section
For governments and health authorities.
Questions about the institutional platform, the Modernize-Transfer-Operate engagement model, and how an institutional partnership runs over its lifetime.
What does Aurora Link offer for governments and health authorities?
An institutional clinical operations platform with six modules (patient record, e-prescribing, eligibility verification, pharmacy inventory, compliance and data protection, continuity), engaged under the Modernize, Transfer, Operate framework. The platform integrates with existing systems, transfers ownership locally over the program term, and continues to be operated by Aurora Link under a service contract for as long as the partner asks it to.
Who owns the infrastructure, source code, and data at the end of the program?
The partner institution. Ownership transfer is structured into the contract from day one, not offered as an option at the end. At program maturity, the technical infrastructure, source code, integration documentation, locally hosted data, and the trained local operations team transfer to the partner.
How long does an institutional engagement take?
It depends on scope. The first phase, a fixed-fee scoping study, is typically 4 to 6 weeks. Initial deployment to reference sites typically runs 6 to 12 months. Extended deployment, transfer, and operate phases each have their own defined duration. The contract puts each phase on an explicit timeline with acceptance criteria.
How is pricing structured?
The first phase is a fixed-fee scoping deliverable that the partner owns regardless of whether the program proceeds. Subsequent phases use milestone-based payments tied to defined deliverables, KPIs, and SLAs. Aurora Link does not run free proofs of concept. The detailed financial structure is shared during the scoping conversation.
Where is the data hosted?
Locally, under the partner's jurisdiction. The platform is deployable on sovereign cloud, local infrastructure, or hybrid arrangements per the partner's policy. Data residency is a design parameter from the first audit, not a post-deployment configuration.
Can Aurora Link operate behind a local prime contractor?
Yes. The shadow operator mode is a fully supported engagement form. Aurora Link supplies the platform, integration, expertise, and operations under a subcontract or teaming agreement with a local prime, who carries the contractual and public face with the institution. The platform, the standards, and the sovereignty commitments are identical to the named-partner mode.
What happens if we decide to take operations in-house, or move to another vendor?
That option is preserved by design. The transfer phase delivers the documentation, source code, integration schemas, and trained local team that any successor operator, internal or external, would need to continue. Aurora Link will cooperate with that transition under the terms of the operate-phase contract.
How does the platform integrate with the systems we already have?
Through standards-based connectors built on FHIR R4 and HL7. Existing HIS, LIS, PACS, pharmacy, insurance, and national identity systems are preserved and made interoperable. Historical data is migrated structurally into the new architecture. Existing IT teams are brought into the program and trained, not displaced.
How is the local team trained?
Capacity transfer is a structured, contractually defined program rather than an afterthought. Local engineers, clinical informaticians, and operations personnel are recruited, trained, and certified during the deployment phases so that, at transfer, they are positioned to operate the platform without external dependency.
What service levels and protections does the operate phase include?
The operate-phase contract defines service-level commitments, incident response procedures, escalation paths, and financial consequences for missed SLAs. The contract also defines a stabilization period with formal acceptance criteria and negotiated exit conditions. Aurora DR (backup and disaster recovery) protects critical clinical data throughout.
For private clinic groups and multi-site networks.
Questions about the Aurora Link Clinic Management System, how it is deployed, how it is priced, and what it covers.
What is the Aurora Link Clinic Management System?
A complete clinic management platform for private clinic groups and multi-site networks. It covers the patient journey from online booking through clinical documentation, e-prescribing, billing and payments, pharmacy and inventory, multi-site management, and AI-assisted workflows.
How long does it take to go live?
Measured in weeks, not years. The path is short by design: a fit call, environment setup and data migration, go-live with role-based training, and ongoing operations on a subscription. The exact timeline depends on practice size, the number of integrations required, and the volume of historical data to migrate.
How does pricing work?
The CMS operates on a direct subscription model. The pricing structure is shared during the fit call and reflects practice size, modules selected, and integrations required. There is no per-module surprise billing and no hidden fee for standard integrations.
Do you migrate data from our existing EHR?
Yes. Data migration from existing EHR and practice management systems is part of the setup phase, before go-live. Common source systems include Epic, Cerner, athenahealth, and AdvancedMD. Patient records, problem lists, medication histories, and billing data are migrated structurally so staff are not retyping anything at go-live.
What systems does the CMS integrate with?
Open APIs to laboratories (Quest, LabCorp), imaging (DICOM-web PACS), pharmacy (NCPDP), and insurance payers (837 / 835 / 270 / 271). FHIR R4 native throughout. Additional integrations can be added on a defined cadence as the practice grows.
Is the CMS HIPAA-compliant?
The CMS is designed and built for HIPAA-grade architecture, with administrative, physical, and technical safeguards aligned to the HIPAA Security Rule. Business associate agreements are entered into where required. Aurora Link does not represent certifications it has not undergone. Specific attestations, audit reports, and security documentation are available on request, scoped to what is current.
Does the CMS support 340B?
Yes. 340B virtual inventory and eligibility verification are part of the inventory module. Controlled-substance traceability under DEA Schedule I through V, dual-witness signatures, biennial inventory tracking, and DEA Form 222 are also part of the standard configuration.
What about ambient AI documentation and AI-assisted coding?
Both are part of the CMS. Ambient documentation generates structured clinical notes from the visit; AI-assisted coding suggests CPT and ICD-10 codes for clinician review. The clinician remains in the loop for all clinical and billing decisions.
What happens if we want to leave?
Your data is yours from day one. The CMS exports patient records, billing, inventory, and operational data in standard formats at any time. There is no proprietary container holding your records, and no exit fee for taking your data with you.
Can we add more sites or modules as the practice grows?
Yes. The CMS is designed for multi-site networks, with a shared data layer across sites and consent-based record portability. Modules are added as needed; you do not pay for what you do not use.
About Aurora Link.
Questions about who Aurora Link is, where it operates, and how the two product lines fit together.
Who is Aurora Link?
Aurora Link LLC is a United States health-technology company, founded in 2024, registered in Burlington, North Carolina. The company designs, deploys, and operates digital health platforms for institutional partners and private clinic networks.
Who is the team?
Aurora Link is led by founder Joseph-Alexander Neya, who brings more than a decade of experience in technology environments where data security and integrity are non-negotiable, including critical infrastructure within a major US defense industrial group, with adjacent experience in healthcare and biotechnology. A certified nurse practitioner serves as clinical advisor. Aurora Link is preparing to formalize its first national-level engagements and its first private-network deployments.
Why both an institutional product and a private clinic product?
The two products serve different market structures with very different procurement, deployment, and pricing dynamics, but they share an engineering core: the same standards, the same security posture, the same integration patterns. Building both reflects a position that a national health system and a private clinic network face the same underlying problems of data portability, clinical workflow, regulatory conformance, and operational continuity.
Why is Aurora Link engaging institutions before broad commercialization?
The value of a digital health platform is fully realized at the system level, not point-solution by point-solution. Engaging institutional partners and established private networks first produces a deployment shape that is coherent, interoperable, and aligned with national or organizational priorities, rather than a fragmented collection of clinic-by-clinic installations.
Where does Aurora Link operate?
The company is based in the United States. Engagements outside the United States are supported under appropriate legal, contractual, and tax structures, including the formation of local operating entities where the deployment structure requires it.
Standards and security.
Questions about the standards Aurora Link implements, how data is protected, and how the platform handles certifications and external networks.
What standards does the platform implement?
FHIR R4 and HL7 for healthcare data exchange. C-CDA and USCDI for document exchange where applicable. SNOMED, LOINC, and ICD-10 for clinical and billing terminology. The International Patient Summary (ISO 27269 / EN 17269) for cross-border emergency access scenarios on the roadmap.
How is data protected?
AES-256 encryption at rest and in transit. Modern identity management with SSO and MFA. Full audit logging with tamper-evident storage. Zero Trust architecture principles applied across the platform. Key management follows industry practice for the deployment environment.
What certifications does Aurora Link hold?
The platform is architected for HIPAA-grade posture and for conformance to national health data protection requirements in the markets where it deploys. Aurora Link does not claim certifications it has not undergone. Specific audit reports, attestations, and certifications are available to prospective partners under appropriate confidentiality terms, scoped to what is current as of the engagement.
Does Aurora Link connect to TEFCA, CommonWell, or Carequality?
Aurora Link's interoperability foundation is designed to support these networks. Specific connectivity is rolled out per engagement and per network on a defined cadence. Current status for a specific network is shared during the fit call.
What about cross-border emergency access?
Cross-border emergency access via the International Patient Summary standard (ISO 27269 / EN 17269) is on the Aurora Link roadmap. The vision is that a citizen abroad can authorize a foreign clinician to access a minimum essential medical summary in an emergency, with patient consent and data sovereignty preserved. This capability is brought online progressively, under governance terms agreed with each partner.
Did not find your answer?
Start a conversation. A 45 to 60-minute session where you ask the questions that matter to you and Aurora Link answers them directly.