Contact Us

Contact Us
First
Last
Sending

Compliance

April 10, 2017

Section 508 Requirements

MedicaSoft is committed to providing high-quality services that are accessible to all of our customers, including individuals with disabilities. MedicaSoft proudly supports Section 508, specifically the Rehabilitation Act (29 U.S.C 794d) that requires Federal agencies to meet specific accessibility standards when buying, developing, maintaining or using information technology. MedicaSoft is committed to ensuring that electronic information is available to as many people as possible. MedicaSoft has strong leadership to guide Section 508 compliance activities including increasing transparency and strengthening accountability across our company. MedicaSoft is committed to improving collaboration regarding electronic information.

DirectTrust Trust Bundle

MedicaSoft participates in multiple Direct connectivity networks, including DirectTrust, where we are a participant in the DirectTrust Accredited Trust Anchor Bundle and the Interoperability Test Bundle.

 

EHNAC Accreditations

MedicaSoft’s HISP is a recipient of the DirectTrust Electronic Healthcare Network Accreditation Commission (EHNAC)’s Direct Trusted Agent Accreditation Program (DTAAP) and the Cloud-Enabled Accreditation Program (CEAP)

Health Level Seven (HL7) International Member

MedicaSoft is a HL7 International Member.

Office of the National Coordinator (ONC) Certification Details – ehr.NXT

This EHR is 2014 Edition Complete EHR Ambulatory and Complete EHR Inpatient certified by an ONC-ACB in accordance with applicable certification adopted by the Secretary of the U.S. Department of Health and Human Services. This certification does not represent an endorsement by the U.S. Department of Health and Human Services.

  • Vendor: MedicaSoft
  • Product Version: ehr.NXT V4.0.1
  • Date Certified: September 10, 2015
  • Effective Date: 2014 Edition
  • Criteria Certified: Complete EHR (Ambulatory and Inpatient)
  • Certification ID Number(s): 09102015-2794-8 (Inpatient) and 09102015-2795-8 (Ambulatory)
  • Modules Tested (Inpatient): 170.314 (a) (1-17); (b) (1-7); (c) (1-3); (d) (1-8); (e) (1); (f) (1-6); (g) (2-4)
  • Modules Tested (Ambulatory): 170.314 (a) (1-15); (b) (1-5, 7); (c) (1-3); (d) (1-8); (e) (1-3); (f) (1-3, 6, 7); (g) (2-4)
  • Clinical Quality Measures Certified (Inpatient): 30v4; 31v3, 32v4; 53v3; 55v3; 60v3; 71v4; 72v3; 91v4; 100v3; 102v3; 104v3; 105v3; 107v3; 110v3; 188v4
  • Clinical Quality Measures Certified (Ambulatory): 2v4; 50v3; 68v4; 69v3; 90v4; 117v3; 126v3; 136v4; 138v3; 146v3; 153v3; 154v3; 155v3; 156v3; 165v3; 166v4
  • Additional Software Used (Ambulatory and Inpatient): None

Costs or Fees

ehr.NXT V4.0.1 enlists third parties for drug database information, such as drug interaction information from First DataBank; e-prescribing network access from Surescripts so that providers may create electronic prescriptions; and patient education information, such as plain-language discharge instructions from Wolters Kluwer’s Lexicomp service. There are one-time costs for each these services that we include in the pricing for ehr.NXT. Each service also involves per-user costs that are typically charged annually or quarterly based on the number of clinical users. We will incorporate these costs into the ehr.NXT pricing agreement.

Providers will need access to HISP services to support Direct Secure Messaging. MedicaSoft charges a connection fee to establish a connection to each customer. This connection allows the customer to send and receive messages via our HISP. HISP services involve transaction costs based on the volume of messages sent, with costs per message declining as volume increases, and these costs will be separate from the ehr.NXT pricing agreement. MedicaSoft’s HISP services have no connectivity restrictions and should support secure messaging with any partners chosen by our customers. Customers are free to choose other HISPs, and MedicaSoft supports connectivity to third party HISPs.

Contractual Limitations

ehr.NXT V4.0.1 requires a contract with MedicaSoft for the implementation and operation of the software. The duration and terms of the contract will vary but typically include a duration of one year or more, specific cancellation terms (i.e. contracts are typically not cancelable without reason), and terms for contract renewal.

MedicaSoft maintains contractual relationships with third parties for drug database information, e-prescribing network access, and patient education information; providers do not need to enter into separate contracts for these services.

Providers will need a separate contract for HISP services to support Direct Secure Messaging. MedicaSoft’s HISP services have no connectivity restrictions and should support secure messaging with any partners chosen by our customers. Customers are free to choose other HISPs, and MedicaSoft supports connectivity to third party HISPs.  

Technical or Practical Limitations

This product has no technical or practical limitations.

ONC Certification Details – HealthCenter

This EHR Module is 2014 Edition compliant and has been certified by an ONC-ACB in accordance with the applicable certification criteria adopted by the Secretary of the U.S. Department of Health and Human Services. This certification does not represent an endorsement by the U.S. Department of Health and Human Services.

  • Vendor: MedicaSoft
  • Product Version: HealthCenter V4.0.1
  • Date Certified: July 30, 2015
  • Effective Date: 2014 Edition
  • Criteria Certified: EHR Module (Ambulatory and Inpatient)
  • Certification ID Number(s): 07302015-2791-8 (Inpatient) and 07302015-2792-8 (Ambulatory)
  • Modules Tested: 170.314(e) (1); (g) (1,4)
  • Clinical Quality Measures Certified: None
  • Additional Software Used: None

Costs or Fees

Providers will need access to HISP services to support Direct Secure Messaging. MedicaSoft charges a connection fee to establish a connection to each customer. This connection allows the customer to send and receive messages via our HISP. HISP services involve transaction costs based on the volume of messages sent, with costs per message declining as volume increases, and these costs will be separate from the HealthCenter pricing agreement. MedicaSoft’s HISP services have no connectivity restrictions and should support secure messaging with any partners chosen by our customers. Customers are free to choose other HISPs, and MedicaSoft supports connectivity to third party HISPs.

Contractual Limitations

HealthCenter V4.0.1 requires a contract with MedicaSoft for the implementation and operation of the software. The duration and terms of the contract may vary but typically include a duration of one year or more, specific cancellation terms (i.e. contracts are typically not cancelable without reason), and terms for contract renewal.

Providers will need a separate contract for HISP services to support Direct Secure Messaging. MedicaSoft’s HISP services have no connectivity restrictions and should support secure messaging with any partners chosen by our customers. Customers are free to choose other HISPs, and MedicaSoft supports connectivity to third party HISPs.

Technical or Practical Limitations

This product has no technical or practical limitations.