1.888.950.0688, option 3 www.vowhs.com info@vowhs.com
Microsoft’s Azure AD is a cloud-based directory and identity management system designed to protect information exchanges. For this release, when you attempt to access the Centricity APIs to generate CCDA documents, Azure AD verifies that you and others within your organization are authorized to do so.
In computer programming, an application program interface (API) is a set of routines, protocols, and tools used to build software applications and promote cross-system interactions. These ‘messenger’ components execute user requests across systems and servers external to your on premise Centricity application, allowing them to collaborate. In simpler terms, APIs take requests to perform actions, convey requests to external systems and servers, and then return the actions requested.
When a provider makes a request in a Centricity system to generate a transition of care document. The clinic server relays the request to Azure AD, which authenticates access to the API server. If authentication is successful, the API server is accessed and supporting CCDA 2.1 APIs are retrieved. The APIs ‘place the order’ within the Centricity system to generate the transition of care document and generates the requested file. In this way, Azure AD provides the layer of security required to ensure secure healthcare information exchanges.
GE API Technology supports Requirements for CDA 2.1 Clinical Visit Summaries Transitions Of Care CDA Exports Activate Patient Access Provides the level of security and authentication required to support healthcare IT solutions. Azure and GE API Technology meets ONC regulations to support advanced and secure healthcare information transfers. The current 1.1 format is the default CCDA version upon upgrading until you switch to the new format .
Active Directory for user authentication Azure Subscription: Business-to-Business (B2B) Azure Active Directory ◦ (AAD) The current 1.1 format is the default CCDA ◦ Azure AD Connect installed on AD servers version upon upgrading until you switch to the new – To sync onsite Active Directory users to your Azure AD format. Free subscription available. Details at: azure.microsoft.com engage.gehealthcare.com
New and Upgraded Content • HTML 5 • CCC Basic V 1.5
New Form Implantable Device Upgraded Forms Family History Social History Care Plan Management
New for Centricity™ Practice Solution 12.3 and Centricity EMR 9.12 • Not backwards compatible • In support of ONC criteria 170.315(a)(14) • Introduces new scanning and import capabilities for device IDs ( Set up required ) • Information is included in CCDA 2.1
Joint Replacement Pacemakers Stents Breast Implants IUD’s
GUDID: Global Unique Device Identifier Database UDI: : Unique Device Identifier • Comprised of the Device Identifier (DI) and the Production Identifier (PI) DI: DI: Device Identifier Mandatory, fixed portion of the UDI that identifies the specific version or model of a device along with the labeler PI PI: Production Identifier Conditional, variable portion of a UDI that identifies one or more of the following: • Lot or batch number • Serial number • Expiration date • Manufacturing date
• Adds new HTML5 technology • Originally Introduced in CPS 12.2 and CEMR 9.10) • Maps to SNOMED codes instead of obs for Quality Reporting support via Mel_ADD_FHX • Improves data collection speed, user experience, updated look-and-feel • Customizable at server level instead of workstation
• Preload previously entered data upon launch • Family and Social History are separated to enable flexibility to use one or both form sets • Checkbox for family history review is automatically checked updating the MU core checklist
New for Centricity™ Practice Solution 12.3 and Centricity EMR 9.12 • Not backwards compatible • In support of ONC criteria 170.315(b)(9) • Introduces a new Care Plan table to store information • Information is included in CCDA 2.1
New Patient Authorization Form Patient Amendments Form Social-Psych-Behavioral Care Plan Revised Vital Signs- Pediatric PE-CCC
Incorporates Azure AD and API technology to meet ONC 2015 criteria New and upgraded clinical content Meets CMS requirements for Quality Payment Program
Recommend
More recommend
