{"id":1648,"date":"2017-07-25T17:43:11","date_gmt":"2017-07-25T17:43:11","guid":{"rendered":"https:\/\/www.emrsystems.net\/blog\/?p=1648"},"modified":"2017-07-25T17:43:11","modified_gmt":"2017-07-25T17:43:11","slug":"eclinicalworks-certification-risk","status":"publish","type":"post","link":"https:\/\/emrsystems.net\/blog\/eclinicalworks-certification-risk\/","title":{"rendered":"eClinicalWorks Just Highlighted 7 Known Certification Risks In Its EHR"},"content":{"rendered":"

The once very popular EHR vendor eClinicalWorks<\/a> has recently circulated a letter to its customers that outlines seven known parts of its Health IT system that it said could cause an EHR certification issue.
\nA news source related to healthcare and information technology managed to procure a copy of the letter, that outlined what eClinicalWorks had done regarding each issue since its $155 million settlement<\/a> with the DoJ in late May.
\nThe first issue reported was \u201cThe blank display of username field in the access logs.\u201d eClinicalWorks stated it had resolved this problem and the better version will be available within the upcoming Q2-2017 Mandatory Patch. The company has also recommended that providers and practice managers using the V10-SP1-C and V10-SP2 editions must update to the new patch immediately as it becomes available. Hospitals and medical groups working with the earlier iterations must update to the new release and then accept the patch.
\nSecond, \u201cthe blank display of Modified By field on the patient\u2019s Problem List.\u201d The company said that it will also resolve this randomly occurring issue, with the imminent Q2 mandatory patch. It further made the same recommendations of installing the latest version to make the patch effective.
\nThe recommended user actions mentioned in the letter seemed to get a bit more complex with the third issue which was related to the structured data transparency of Social history. eClinicalWorks termed the risk as the incapacity of social history data entries to update themselves in the Progress Notes table regarding the calculation of social history measures for inactive programs at the back end. The company said that installing the patch will fix this issue and it also developed a report containing patient records that were affected by this. After the acceptance and installation of the patch, the report can be retrieved from the Reports menu > Report Console. The Structured Social History Report will be located among the Advisory Reports. Logically, eClinicalWorks recommends users to run the report and utilize their findings in identifying patients having such discrepancies. When the discrepancies are found the users should update accordingly.
\nThe fourth issue was observed to be similar to the preceding problems which was \u201cLack of display of imported CCD files in patient documents preview.\u201d This occurred when CCD file sheets failed to align with eClinicalWorks style sheet. The Q2-2017 patch is expected to fix this problem.
\nNow the fifth issue was Drug Interaction window\u2019s incorrect issue date. This issue was only with the browser edition of V10-SP2. \u00a0The sixth issue mentioned also resided only within the browser version. It was the missing Printing Rx Education in patient logs and affected the meaningful use Objective Measure 6. The company said that it will be amended in the forthcoming mandatory patch.
\nThe seventh and final issue was related to the Printing patient education which was missing in patient education logs. This issue was also only found in the browser version and pertained to meaningful use Objective Measure 6.<\/p>\n","protected":false},"excerpt":{"rendered":"

The once very popular EHR vendor eClinicalWorks has recently circulated a letter to its customers that outlines seven known parts of its Health IT system that it said could cause an EHR certification issue. A news source related to healthcare and information technology managed to procure<\/p>\n","protected":false},"author":8,"featured_media":1649,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[19],"tags":[149,179,184,228],"class_list":["post-1648","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-healthcare-news","tag-ehr-software-solution","tag-emr-systems","tag-emr-vendors","tag-healthcare-it-providers"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/emrsystems.net\/blog\/wp-json\/wp\/v2\/posts\/1648","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/emrsystems.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/emrsystems.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/emrsystems.net\/blog\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/emrsystems.net\/blog\/wp-json\/wp\/v2\/comments?post=1648"}],"version-history":[{"count":0,"href":"https:\/\/emrsystems.net\/blog\/wp-json\/wp\/v2\/posts\/1648\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/emrsystems.net\/blog\/wp-json\/wp\/v2\/media\/1649"}],"wp:attachment":[{"href":"https:\/\/emrsystems.net\/blog\/wp-json\/wp\/v2\/media?parent=1648"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/emrsystems.net\/blog\/wp-json\/wp\/v2\/categories?post=1648"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/emrsystems.net\/blog\/wp-json\/wp\/v2\/tags?post=1648"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}