awg discussion 12-06-11

4
AWG Discussion 12-06-11 Peter Li, [email protected]

Upload: miron

Post on 17-Jan-2016

38 views

Category:

Documents


0 download

DESCRIPTION

AWG Discussion 12-06-11. Peter Li, [email protected]. OSEHRA/Vista Product Definition and Roadmap Deliverable. There are 172 modules on the list. 138 modules are considered “Core FOIA” Six modules have no documentations. 16 modules have Window GUI components. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: AWG Discussion 12-06-11

AWG Discussion 12-06-11

Peter Li, [email protected]

Page 2: AWG Discussion 12-06-11

OSEHRA/Vista Product Definition and Roadmap Deliverable

There are 172 modules on the list.– 138 modules are considered “Core FOIA”

• Six modules have no documentations.• 16 modules have Window GUI components.• 1 module, Care Management/Heathvet Desktoop will not be used by VA• 1 module, Immunology Case Registry has been replaced by Clinical Case Registry.

– 34 modules are considerd non-Core FOIA• 5 modules are vendor SW• 11 modules are HealtheVet modules.• VA enterprise systems , e.g., Clinical/Health Data Repository (CHDR),

Health Eligibility Center, Nationwide Health Information Network Adapter, etc.

• VA specific utiltities, e.g., National Patch Module, SlotMaster, etc.• Modules that uses Web GUI as the primary interface.

Criteria for a “Core FOIA” module - must have MUMP components in the current FOIA release and clients (usually Windows GUI client) available for download from the VA download site.

Page 3: AWG Discussion 12-06-11

Confusion associated with Modules, Package, and Namespace

• Example: Ambulatory Care Reporting, an add-on to Scheduling Package• Module Name: Ambulatory Care Reporting • FOIA Package Name – Scheduling, Registration, and PCE

based on three patches: SD*5.3*66, DG*5.3*139, and PX*1.0*41

• Namespace: SD, DG, PCE – the release note indicated installation of routines in Scheduling, Registration, and Patient Care Encounter Namespace.

Page 4: AWG Discussion 12-06-11

System Architecture Update

• Verified and updated the module dependencies diagrams – mostly the installation and ICR dependencies.

• Added ICR dependencies to the diagram if the ICRs are mentioned in the documentation.

• Added public ICRs, Files, and Globals references for each module. Source of the public ICRs - ICRs-Interface Control Registrations - APPROVED PUBLIC DETAIL 20110926 from Julie Harvey. The source of the Files and Globals - File Custody DEC 13 2010.xls from VA download site.