Title | Due date | Budget | Progress | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cooper Dev
Cooper development items
|
Overdue | Mar 05, 2012 |
|
|
|||||||||||||||||||||||
Cooper Config
Configuration issues
|
Overdue | Mar 05, 2012 |
|
||||||||||||||||||||||||
Open Source Package
These issues are for improving the experience of people downloading the open source package for the first time. This includes product improvements, setup package, documentation, configuration, etc.
|
Overdue | Mar 31, 2012 |
|
|
|||||||||||||||||||||||
Cooper Support
Cooper Support Items
|
Overdue | Mar 31, 2012 |
|
|
|||||||||||||||||||||||
Overdue | May 01, 2012 |
|
|
||||||||||||||||||||||||
Backlog
Put your to-do's and feature requests here. Pull them into the current milestone when you are ready to work on them.
|
Overdue | Dec 31, 2012 |
|
|
|||||||||||||||||||||||
Verify and Document MU items that should already pass
§170.302 c, d, e, f, g, h, i, m, o, q, r, t
§170.304 a, c, d |
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.302 (j) Medication reconciliation
Enable a user to electronically compare two or more medication lists.
|
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.302 (k) Submission to immunization registries
Electronically record, modify, retrieve, and submit immunization information in accordance with:
(1) The standard (and applicable implementation specifications) specified in §170.205(e)(1) or §170.205(e)(2); and (2) At a minimum, the version of the standard specified in §170.207(e). |
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.302 (u) General encryption
Encrypt and decrypt electronic health information in accordance with the standard specified in §170.210(a)(1), unless the Secretary determines that the use of such algorithm would pose a significant security risk for Certified EHR Technology.
|
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.302 (w) (Optional) Accounting of disclosures
Accounting of disclosures. Record disclosures made for treatment, payment, and health care operations in accordance with the standard specified in §170.210(d).
|
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.304 (f) Electronic copy of health information
Enable a user to create an electronic copy of a patient’s clinical information, including, at a minimum, diagnostic test results, problem list, medication list, and medication allergy list in:
(1) Human readable format; and (2) On electronic media or through some other electronic means in accordance with: (i) The standard (and applicable implementation specifications) specified in §170.205(a)(1) or §170.205(a)(2); and (ii) For the following data elements the applicable standard must be used: (A) Problems. The standard specified in §170.207(a)(1) or, at a minimum, the version of the standard specified in §170.207(a)(2); (B) Laboratory test results. At a minimum, the version of the standard specified in §170.207(c); and (C) Medications. The standard specified in §170.207(d). |
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.304 (g) Timely access
Enable a user to provide patients with online access to their clinical information, including, at a minimum, lab test results, problem list, medication list, and medication allergy list.
|
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.304 (h) Clinical summaries
Enable a user to provide clinical summaries to patients for each office visit that include, at a minimum, diagnostic test results, problem list, medication list, and medication allergy list. If the clinical summary is provided electronically it must be:
(1) Provided in human readable format; and (2) Provided on electronic media or through some other electronic means in accordance with: (i) The standard (and applicable implementation specifications) specified in §170.205(a)(1) or §170.205(a)(2); and (ii) For the following data elements the applicable standard must be used: (A) Problems. The standard specified in §170.207(a)(1) or, at a minimum, the version of the standard specified in §170.207(a)(2); (B) Laboratory test results. At a minimum, the version of the standard specified in §170.207(c); and (C) Medications. The standard specified in §170.207(d). |
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.304 (i) Exchange clinical information and patient summary record
(1) Electronically receive and display. Electronically receive and display a patient’s summary record, from other providers and organizations including, at a minimum, diagnostic tests results, problem list, medication list, and medication allergy list in accordance with the standard (and applicable implementation specifications) specified in §170.205(a)(1) or §170.205(a)(2). Upon receipt of a patient summary record formatted according to the alternative standard, display it in human readable format.
(2) Electronically transmit. Enable a user to electronically transmit a patient summary record to other providers and organizations including, at a minimum, diagnostic test results, problem list, medication list, and medication allergy list in accordance with: (i) The standard (and applicable implementation specifications) specified in §170.205(a)(1) or §170.205(a)(2); and (ii) For the following data elements the applicable standard must be used: (A) Problems. The standard specified in §170.207(a)(1) or, at a minimum, the version of the standard specified in §170.207(a)(2); (B) Laboratory test results. At a minimum, the version of the standard specified in §170.207(c); and (C) Medications. The standard specified in §170.207(d). |
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.304 (j) Calculate and submit clinical quality measures
(1) Calculate
(i) Electronically calculate all of the core clinical measures specified by CMS for eligible professionals. (ii) Electronically calculate, at a minimum, three clinical quality measures specified by CMS for eligible professionals, in addition to those clinical quality measures specified in paragraph (1)(i). (2) Submission. Enable a user to electronically submit calculated clinical quality measures in accordance with the standard and implementation specifications specified in §170.205(f). |
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.302 (l) Public health surveillance
Electronically record, modify, retrieve, and submit syndrome-based public health surveillance information in accordance with the standard (and applicable implementation specifications) specified in §170.205(d)(1) or §170.205(d)(2).
|
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.302 (n) Automated measure calculation
For each meaningful use objective with a percentage-based measure, electronically record the numerator and denominator and generate a report including the numerator, denominator, and resulting percentage associated with each applicable meaningful use measure.
|
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.302 (p) Emergency access
Permit authorized users (who are authorized for emergency situations) to access electronic health information during an emergency
|
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.302 (r) Audit log
(1) Record actions. Record actions related to electronic health information in accordance with the standard specified in §170.210(b).
(2) Generate audit log. Enable a user to generate an audit log for a specific time period and to sort entries in the audit log according to any of the elements specified in the standard at §170.210(b). |
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.302 (s) Integrity
(1) Create a message digest in accordance with the standard specified in §170.210(c).
(2) Verify in accordance with the standard specified in §170.210(c) upon receipt of electronically exchanged health information that such information has not been altered. (3) Detection. Detect the alteration of audit logs. |
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
Provide summary of care for transferred patients
The EP, eligible hospital or CAH who transitions their patient to another setting of care or provider of care or refers their patient to another provider of care should provide summary care record for each transition of care or referral.
|
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
Protect electronic health information
45 CFR 164.308(a) A covered entity must, in accordance with §164.306:
(1)(i) Standard: Security management process. Implement policies and procedures to prevent, detect, contain, and correct security violations. (ii) Implementation specifications: (A) Risk analysis (Required). Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information held by the covered entity. (B) Risk management (Required). Implement security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level to comply with §164.306(a). (C) Sanction policy (Required). Apply appropriate sanctions against workforce members who fail to comply with the security policies and procedures of the covered entity. (D) Information system activity review (Required). Implement procedures to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports. |
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.302 (a) Drug-drug, drug-allergy interaction checks
(1) Notifications. Automatically and electronically generate and indicate in real-time, notifications at the point of care for drug-drug and drug-allergy contraindications based on medication list, medication allergy list, and computerized provider order entry (CPOE).
(2) Adjustments. Provide certain users with the ability to adjust notifications provided for drug-drug and drug-allergy interaction checks. |
Overdue | Mar 03, 2013 |
|
|
|||||||||||||||||||||||
§170.302 (b) Drug formulary checks
Enable a user to electronically check if drugs are in a formulary or preferred drug list.
|
Overdue | Mar 03, 2013 |
|
|
Home / Developer API / Tour / Get a Project - Solutions for Bug & Issue Tracking, Collaboration Tools, Subversion Hosting, Git Hosting
Encounterpro-os is powered by Assembla.