Certified Healthcare IT
Products listed on the ONC Certified Health IT Product List (CHPL) have been successfully tested by an ATL and certified by an ONC-ACB. Providers and Hospitals use the CHPL to identify certified health IT and generate the CMS EHR Certification ID required for meaningful use attestation.
ONC CERTIFIED HIT® is a registered trademark of HHS.
| Certification | ONC Health IT |
| Classification | Modular |
| Practice Type | Ambulatory |
| Developer Name | Brilogy Corporation |
| Product Name | AXEIUM |
| Version | MU3 |
| Certificate No. | 15.05.05.1171.BRIL.02.01.1.221219 |
| Certificate Date | 12/19/2022 |
| Cert. Updated | 12/27/2024 |
SLI has been authorized to perform Complete Electronic Health Record (EHR) testing for certification by the US Department of Health and Human Services' Office of the National Coordinator as an Accredited Test Lab (ONC-ATL).
Testing by an ATL will signify to eligible professionals that an EHR technology has the capabilities necessary to support their efforts to meet the goals and objectives of meaningful use.
SLI CERTIFIED® is a registered trademark of Gaming Laboratories International, LLC dba SLI Compliance.
Ambulatory EHR - Certified Modules
Clinical Quality Measures (eCQMs)
Ambulatory EHR - Additional Required Software
Additional software that is relied on to comply with one or more of the certification criteria includes:
Direct Message
(via a web portal provided by MDToolbox that is certified to the Surescripts HISP)
Direct Message capability augments other ways (Secure Email, FAX, SMS) of exchanging secure health information over the Internet.
Secure Email
(via web services provided by Paubox)
Secure Email capability augments other ways (Direct Message, FAX, SMS) of exchanging secure health information over the Internet.
Ambulatory EHR Modules - Costs
Pricing and Disclosures:
AXEIUM is a cloud-based system that supports access via web browsers, mobile apps (iOS/Android), and Windows desktop clients.
Rather than a per provider fee, license fees are the combination of a monthly subscription fee, which represents the minimum charge and covers the cost of system updates, plus a usage fee, which is typically favorable to clinics as they typically have a workforce mix comprised of full time, part time, and volunteer workers.
Additional Health Information Technology, software and/or hardware, is required for some features, such as ePrescribe, eFax, eMail, SMS, ePhone, eVideo, eSign, as well as licenses and/or subscriptions may be needed for third-party copyrighted materials and APIs, for which Client is either directly subscribed, or receives pass-through billing.
Notes & Disclaimers
- All implementations are subject to a one-time installation cost and a monthly subscription fee.
- You may be eligible for discounts based on volume, or if you are a member of a participating collective.
- Additional transaction charges may be imposed by 3rd party vendors for optional subscription services, e.g., SMS appointment reminders.
- An integration fee may apply for each subscribed interface, e.g., labs, dental radiography, retinal image capture, mammography, HIEs, mobile app, etc.
- An additional monthly maintenance fee may be required for each subscribed interface.
- An additional monthly subscription fee is required for each prescriber to formulate and transmit eRx on the Surescripts network.
- An additional monthly subscription fee is required for each provider subscribed to the Surescripts network for DIRECT messages.
- An additional monthly subscription fee is required for eVideo, eFax, eSMS, and Secure Email service providers, if these features are subscribed.
- Prices are subject to change without notice.
Meaningful Use Disclosures
AXEIUM relies on the following additional software to demonstrate compliance as an ONC-certified Electronic Medical Records system:
- MDToolbox provides subscription services to the Surescripts DIRECT Message network.
- Paubox provides subscription services for secure email.
Transparency Attestation
It is your data that is stored on your servers, and with the exception of third party fees for ePrescribe, DIRECT messaging, secure email, and secure text messaging, an eligible provider should incur no additional costs either to meet supported meaningful use objectives and measures or to achieve any other use within the scope of the Health IT Module's certification.
To support transparency in the marketplace, Brilogy Corporation will voluntarily and timely provide, in plain writing and in a manner calculated to inform, any part (including all of) the information required to be disclosed under paragraph (k)(1) of § 45 CFR 170.523:
(A) to all customers, prior to providing or entering into any agreement to provide any certified health IT or related product or service;
(B) to any person who requests or receives a quotation, estimate, description of services, or other assertion or information from the developer in connection with any certified health IT or any capabilities thereof; and
(C) to any person, upon request.
Multi-Factor Authentication
The system supports multi-factor authentication when access is requested from a mobile device.
Ambulatory EHR - API Documentation
Application Programming Interfaces (APIs) allow direct access to data elements of a patient's electronic health record to the extent permissible under applicable privacy laws. Developers can use the AXEIUM APIs to create applications that interact with electronic health data via a RESTful API based on the FHIR standard.
Authentication
Before you can access patient information you must register to the Clinic's Patient Portal at {domain-url}/#/account
Patient Selection — 45 CFR 170.315(g)(7)
API returns a patient-specific token, which is then used as a parameter when calling the data access endpoints. The account must be setup to have access to the patient requested, and First Name, Last Name, and DOB are required. Count Only will only return the count.
All Data Request — 45 CFR 170.315(g)(9)
API access to all patient data specified in the USCDI Data Set, for a specific date or date range. Note that the PatientId parameter is not required when authenticated as a single patient. If requesting data for all time, pass null or do not specify the StartDate or EndDate parameters. In order to get patient data for a specific date, parameters StartDate and EndDate must be the same.
PatientId : string (optional)
StartDate : string format "YYYY-MM-DD" (optional)
EndDate : string format "YYYY-MM-DD" (optional)
Sample Request:
Method: POST
URL:
{domain-url}/api/external/pd/v1/patient/PatientData