None
| Info |
|---|
This Complete EHR is 2015 Edition compliant and has been certified by an ONC-ACB in accordance with the applicable certification criteria adopted by the Secretary of Health and Human Services. This certification does not represent an endorsement by the U.S. Department of Health and Human Services. Certified Health IT Product List (CHPL): |
Developer | NeoDeck Holdings Corp. |
|---|---|
Product Name & Version | NeoMed 4 |
Date Certified |
Certification ID | 15.04.04.2814.NeoM.04. |
|---|
02.1. |
221230 | |
Certification Criteria | § 170.315(a)(1,2,3,4,5,9 |
|---|
,12, |
14, |
15) |
10) |
|
,3) |
) |
CQMs |
|---|
CMS69v4
CMS122v4
CMS127v4
CMS130v4
CMS131v4
CMS134v4
CMS138v4
CMS147v4
CMS155v4
CMS156v4
CMS163v4
CMS165v4
| |
Additional Software |
|
|---|
Costs and Fees |
|
|---|---|
Additional Costs |
|
Additional Infomation |
|
Technical or Practical Requirements |
|
Contractual Requirements |
|
Third Party |
|
Costs and Fees of Certified Health IT
Capability | Description of Capability | Costs or Fees | Contractual Requirements | Technical or Practical Requirements | |
|---|---|---|---|---|---|
Types of costs or fees that a user may be required to pay to purchase, license, implement, maintain, upgrade, use, or otherwise enable and support the use of the implementation or use of the capability -OR- in connection with the data generated in the course using the capability | Requirements of a contractual nature (including developer policies and other business practices) that a user may encounter in the implementation or use of the capability -OR- in the connection with the data generated in the course of using the capability | Require;ments of a technical or practical nature that a user may encounter that could prevent or impair the successful implementation, configuration, maintenance, support or use of the capability -OR- prevent or limit the use, exchange or portability of any data generated in the course of using the capability | |||
170.315(a)(1) | Computerized provider order entry (CPOE) – medications | This functionality enables users to place medication orders electronically. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(a)(2) | CPOE – laboratory | This functionality enables users to place laboratory orders electronically. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(a)(3) | CPOE – diagnostic imaging | This functionality enables users to place diagnostic imaging orders electronically. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(a)(4) | Drug-drug, drug-allergy interaction checks for CPOE | This functionality enables users to be alerted for potential drug interaction alerts before they complete medication orders in the patient's chart. NeoMed uses the GoldStandard Medication database to obtain this information. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(a)(5) | Demographics | Enables NeoMed to capture demographic data as part of the registration process. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(a)(9) | Clinical decision support | Enable real time alerts at the point of care based on patient specific information. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(a)(10) | Drug-formulary and preferred drug list checks | This functionality enables a CEHRT user to perform Drug Formulary checks during medication prescriptions. This functionality is included in Neomed and utilizes the Surescripts eligibility files to determine formulary coverage. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(a)(12) | Family health history | This functionality enables the user to electronically record, change and access a patient’s family health history | |||
See Costs and Fees above.
None
See Technical or Practical Requirements above.
170.315(a)(13)
Patient-specific education resources
. | See Costs and Fees above. | None | See Technical or Practical Requirements above. | ||
170.315(a)(14) | Implantable device list | This functionality enables capture of patient implantable device data as history in their chart. The certified EHR interacts with FDA Webaccess GUDID to incorporate the device ID and Unique device Identifiers for the implantable device. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(b)(1) | Transitions of Care | See Costs or Fees above | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(b)(2) | Clinical information reconciliation and incorporation | This functionality enables a user to electronically reconcile problems, medication allergies, medications, and immunizations listed in an incoming transition of care/referral summary C-CDA format to against the patient's medication list, problem list, medication-allergy list, and immunization list in the NeoMed. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(b)(3) | Electronic Prescribing | Complete with drug-drug interaction checks, allergy checking and plan-specific formularies, this functionality enables a user to prescribe and route prescriptions directly from the exam room to the patient’s preferred pharmacy for faster fulfillment. The solution uses RxNorm and NCPD standards, and the SureScripts infrastructure for prescription transmission to the pharmacy. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(b)( |
10) |
Electronic Health Information export | This functionality enables a user to electronically create a set of export summaries for all patients in C-CDA format that represents the most current clinical information about each patient. It includes clinical data defined in the Common Clinical Data Set, the reason for referral, and the referring or transitioning provider’s name and office contact information. | See Costs and Fees above. | None | See Technical or Practical Requirements above. | |
170.315(c)(1) | Clinical quality measures (CQMs) – record and export | This functionality enables a user to electronically capture and export all the data necessary to calculate each of the NeoMed-supported Clinical Quality Measures (CQM), including the codification of CQM exceptions and exclusion. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(c)(2) | CQMs – import and calculate | This functionality enables a user to electronically capture and export all the data necessary to calculate each of the NeoMed-supported Clinical Quality Measures (CQM), including the codification of CQM exceptions and exclusion. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(c)(3) | CQMs – report | This functionality enables a user to electronically create a data file for transmission of Clinical Quality Measures (CQM) data according to the Quality Reporting Document Architecture standard. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(c)(4) | CQMs – filter | This functionality enables a user to filter CQM data after generation. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(d)(1) | Authentication, access control, authorization | Enables the system administrator to control user access to all the areas of the NeoMed EHR. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(d)(2) | Auditable events and tamper-resistance | Prevents and detects modifications to the system's audit log. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(d)(3) | Audit report(s) | Provides detailed reports of all activity that has occurred in the system by all users. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(d)(4) | Amendments | Enable users to ammend existing records while preserving previous data and recording all changes in the audit log. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(d)(5) | Automatic access time-out | Causes NeoMed to log out after a set period of time if there is no activity by the user. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(d)(6) | Emergency access | Enable administrative users to permit emergency access to patient health information for users who are not otherwise authorized | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(d)(7) | End-user device encryption | Encrypts data at rest on user devices. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(d)(8) | Integrity | Ensures that data has not been changed in transit while users are connected to the system. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(d)(9) | Trusted connection | Ensures that all communications to the system are encrypted while in transit. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(d)(12) | Encrypt Authentication Credentials | Attestation to whether NeoMed encrypts authentication credentials. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(d)(13) | Multi-factor Authentication | Attestation to whether NeoMed supports multi-factor authentication. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(e)(1) | View, download, and transmit to 3rd party | This functionality enables patients to view, download or transmit their health information in the PatientVault portal or app that was transmitted from the NeoMed EHR. The data contains all the information selected to be included on the C-CDA for the patient, including the common clinical data set and other data such as notes and documents. Any time a patient has a new encounter, the data will be uploaded to the portal. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(e)( |
Secure messaging
This functionality enables users to send and receive secure messages to/from patients in the EHR using the PatientVault portal / app. Secure messages may be initiated by the provider using the EHR or the patient using the patient portal, and may include clinical data, administrative data, and other information. All this functionality is already integrated into NeoMed and accessible to all users.
See Costs and Fees above.
None
See Technical or Practical Requirements above.
3) | Patient health information capture | This functionality enables user to capture patient health information into the chart to support better patient engagement in their care. PatientVault can be utilized to provide this data in addition to other EHR functions. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(f)(2) | Transmission to public health agencies – syndromic surveillance | This functionally enables the EHR to electronically create syndrome-based public health surveillance information for electronic transmission in accordance to the HL7PHIN Messaging standard for Syndromic Surveillance. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(g)(2) | Automated measure calculation | Enables NeoMed to record and calculate Meaningful Use objective measures. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(g)(3) | Safety-enhanced design | Enables NeoMed to meet the usability guidelines for end users. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(g)(4) | Quality system management | This functionality enables use of certified EHR technology for users with disability. Professional EHR adhered to WCAG 2.0 standards. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(g)(5) | Accessibility-centered design | This functionality enables users with disabilities to use the PatientVault portal. PatientVault meets the WCAG 2.0 A level. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |
170.315(g)(6) | Consolidated CDA creation performance | This functionality certifies the CDA performance for all CDA documents generated from certified EHR to ONC prescribed standards |
See Costs and Fees above.
None
See Technical or Practical Requirements above.
170.315(g)(7)
Application access – patient selection
This functionality enables the patient to connect to their record with any third party engagement app using the PatientVault REST API.
See Costs and Fees above.
None
See Technical or Practical Requirements above.
170.315(g)(8)
Application access – data category request
This functionality enables the patient to connect to their record with any third party engagement app using the PatientVault REST API and retrieve areas of the Common Clinical Data Set
See Costs and Fees above.
None
See Technical or Practical Requirements above.
170.315(g)(9)
Application access – all data request
. | See Costs and Fees above. | None | See Technical or Practical Requirements above. | ||
170.315(h)(1) | Direct Project | This functionality allows certified EHR to connect with any HIE and demonstrate interoperability using DIRECT protocols. | See Costs and Fees above. | None | See Technical or Practical Requirements above. |