The ONC Jira Core and Confluence support team will soon implement an account deactivation policy for all users who have not logged into the systems within the previous 90-days or more. To avoid the risk of having your account being deactivated, please immediately log into ONC Jira Core and Confluence as soon as possible.
Accounts that are deactivated will be retained, including historic activity. Users are able to reactivate their accounts using the correct credentials used prior to deactivation. If a user has forgotten their usernames or passwords, they can email onc-jira-questions@healthit.gov to request reactivation.
Reminder: Do not include any PHI or PII in JIRA. If you require 508 accessibility assistance, then please send an email to onc-jira-questions@healthit.gov
Login Support: If you encounter a captcha prompt, login issues, or believe your account may be deactivated and require assistance, please send an email to onc-jira-questions@healthit.gov
2 Comments
Anonymous
The Michigan ACRS provides a good focused use case of sharing basic info (Who, here, when, high level what) to drive "situational awareness" as Tim described it. That awareness can then be used to drive more detailed queries for data. We need to focus on prioritized foundation use cases like sharing of basic information and get that information flowing broadly via solutions like PCDH and ACRS and then we will have drivers for more advanced use cases including query and many others.
Anonymous
Agree with getting the fundamentals - such as who, what, when, where, why (W5) - in place as foundational to full interoperability. This is a key emphasis of the following standards: ISO/HL7 10781 EHR System Functional Model Release 2, Record Infrastructure Section (2014) (http://www.hl7.org/implement/standards/product_brief.cfm?product_id=269), ISO 21089 Trusted End-to-End Information Flows (2017 version approved and in publication) and FHIR STU-3 Record Lifecycle Event Implementation Guide (http://hl7.org/fhir/ehrsrle/ehrsrle.html) including FHIR STU-3 AuditEvent (http://www.hl7.org/FHIR/ehrsrle/ehrsrle-auditevent.html) and FHIR STU-3 Provenance (http://www.hl7.org/FHIR/ehrsrle/ehrsrle-provenance.html) resources. See also the FHIR STU-3 W5 Report (http://hl7.org/fhir/w5.html) and the FHIR STU-3 Implementer's Safety Checklist, Item #9 (http://hl7.org/fhir/safety.html).