1.888.950.0688, option 3 www.vowhs.com info@vowhs.com Microsofts - - PowerPoint PPT Presentation

▶
1 888 950 0688 option 3 vowhs com info vowhs com
SMART_READER_LITE
LIVE PREVIEW

1.888.950.0688, option 3 www.vowhs.com info@vowhs.com Microsofts - - PowerPoint PPT Presentation

Feb 08, 2024 18 likes •520 views

1.888.950.0688, option 3 www.vowhs.com info@vowhs.com Microsofts 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

slide-1
SLIDE 1

1.888.950.0688, option 3 info@vowhs.com www.vowhs.com

slide-2
SLIDE 2
slide-3
SLIDE 3
slide-4
SLIDE 4

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.

slide-5
SLIDE 5

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.

slide-6
SLIDE 6

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.

slide-7
SLIDE 7

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.

slide-8
SLIDE 8

 Active Directory for user authentication  Azure Subscription:

  • Business-to-Business (B2B) Azure Active Directory

(AAD)

  • Azure AD Connect installed on AD servers

– To sync onsite Active Directory users to your Azure AD Free subscription available. Details at: azure.microsoft.com engage.gehealthcare.com

The current 1.1 format is the default CCDA version upon upgrading until you switch to the new format.

slide-9
SLIDE 9

 New and Upgraded Content

  • HTML 5
  • CCC Basic V 1.5
slide-10
SLIDE 10

New Form Implantable Device Upgraded Forms Family History Social History Care Plan Management

slide-11
SLIDE 11

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
slide-12
SLIDE 12

 Joint Replacement  Pacemakers  Stents  Breast Implants  IUD’s

slide-13
SLIDE 13

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

  • f the following:
  • Lot or batch number
  • Serial number
  • Expiration date
  • Manufacturing date
slide-14
SLIDE 14
slide-15
SLIDE 15
slide-16
SLIDE 16
  • 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
slide-17
SLIDE 17
  • 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

slide-18
SLIDE 18
slide-19
SLIDE 19
slide-20
SLIDE 20
slide-21
SLIDE 21
slide-22
SLIDE 22
slide-23
SLIDE 23
slide-24
SLIDE 24
slide-25
SLIDE 25
slide-26
SLIDE 26
slide-27
SLIDE 27

 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
slide-28
SLIDE 28
slide-29
SLIDE 29
slide-30
SLIDE 30
slide-31
SLIDE 31
slide-32
SLIDE 32
slide-33
SLIDE 33

New

 Patient Authorization Form  Patient Amendments Form  Social-Psych-Behavioral  Care Plan

Revised

 Vital Signs- Pediatric  PE-CCC

slide-34
SLIDE 34
slide-35
SLIDE 35
slide-36
SLIDE 36
slide-37
SLIDE 37
slide-38
SLIDE 38
slide-39
SLIDE 39
slide-40
SLIDE 40
slide-41
SLIDE 41
slide-42
SLIDE 42
slide-43
SLIDE 43
slide-44
SLIDE 44
slide-45
SLIDE 45
slide-46
SLIDE 46
slide-47
SLIDE 47
slide-48
SLIDE 48
slide-49
SLIDE 49

 Incorporates Azure AD and API technology to

meet ONC 2015 criteria

 New and upgraded clinical content  Meets CMS requirements for Quality Payment

Program

slide-50
SLIDE 50