Weekly Open-Source EHR - Architecture Work Group (AWG)

DATE & TIME: Every Tuesday 4:00 pm ET WebEx: https://tiag.webex.com/

PHONE:  +1-408-600-3600      Access code: 629 453 409 or use VOIP

DOCUMENTS at: http://www.osehra.org/node/47/content/documents

DISCUSSION at: http://www.osehra.org/node/47/content/discussions

WIKI at: http://www.osehra.org/node/47/content/wikis

HTML SYSTEM ARCHITECTURE at: http://architecture.osehra.org … can be viewed with a web browser.


The OSEHRA-VistA Visual Cross-Reference codebase-documentation is based on an automated XINDEX analysis and can be accessed directly via http://code.osehra.org/dox or from the OSEHRA web page -> Resources ->Development Tools -> Web Based Code Review.


  • Joining OSEHRA is free; please join.
  • Please join the OSEHRA AWG at: http://www.osehra.org/groups to receive AWG e-mail.
  • Please provide suggestions for Visual Cross-Reference map improvements, such as:
  1. For each global-file, graph/list the modules/routines, which read-or-write to the global file (e.g., this would verify ICR completeness and compliance)
  2. For each module/routine, list its version & applicable patches; this may require a configuration file.
  3. For each patch, list their module dependencies; this may require a configuration file.
  4. For each module, list its Install-dependencies on other modules and their versions; this may require a configuration file.
  5. For each Package/module/patch add links to online VistA Documentation Library (VDL); this may require a configuration file.
  6. Stub out non-MUMPS modules, so they can be part of the Visual Cross Reference Map and Product Definition (potentially this can be done as part of the configuration file.
  7. Identify and trace threads-of-execution throughout the system to support regression path-testing.
  8. Identify unused entry points and globals (dead code)
  9. The Visual Cross Reference Map tool should be able to export a comma separated file as a configuration management “Product Definition”, which is suitable for Excel or database import.


AUTOMATED SYSTEM ARCHITECTURE and PRODUCT DEFINITION CERTIFICATION TOOL PROPOSAL: OSEHRA’s Visual Cross-Reference utility should be expanded to define OSEHRA System-Architecture and “Product Definitions” for any configuration of MUMPS modules, including Class III configurations at each facility.

  • If the Visual Cross-Reference utility is given one configuration file, it should generate the complete system architecture and “Product Definition” for that configuration.
  • If the Visual Cross-Reference utility is given two configuration files, it should also produce the map-and-gap between the two Product Definitions. The map-and-gap of package, module, routine, global cross-reference maps would be very helpful in architectural test-and-certification and to help identify necessary regression-test pathways. Each Product-Definition configuration-file should include the list of VistA and environment (e.g., GT.M, LINUX) modules & patches defining a Product Definition:
    1. Module/patch Name
    2. Module/patch Version
    3. Module/patch Description [optional]
    4. Module/patch user, install technical Documentation VDL link [optional]
    5. Module/patch test/certification documentation [optional]
    6. Applicable patches and required patch order
      • Impacted modules
      • Impacted globals
    7. For custodial modules/patches, applicable Interface Control Agreements (ICRs)
      • ICR number and date
      • Custodial Module/patch Name
      • Global involved,
      • Modules involved
    8. Applicable Namespaces for the module
    9. Comments to be included in the Product Definition output.


JUSTIFICATION: the proposed changes allow the automatic generation of comprehensive system architectures and “Product Definitions” and architectural certification for any configuration of MUMPS modules/routines. The only system architecture missing parts will be:

  • Interface Design Specifications for each module/routine.
  • Deployment views
  • Requirements traceability
  • System Functional Descriptions
  • Operational Activities mapped to System Functions/Services
  • Information Models

If desired, these can be manually added.


Between September and December, the 2011 System Architecture baseline will be validated and the future-state n-tiered EHR Services Platform (ESP) architecture for plug-&-play applications and data-store Software Development Kit (SDK) Conceptual Architecture and Implementation Guide (IG) will be defined. In 2012, the OSEHRA Product Definition baseline (e.g., certified “gold version”) and transition Roadmap to the future-state ESP architecture will be defined.  



               (Related slides & spread sheets are posted at the “Documents” link given above)

  1. Start: Introductions and Roll Call
  2. Minutes: Approve last week’s minutes and review this week’s agenda
    1. OSEHRA-VISTA visual Cross Reference at: http://code.osehra.org/dox/ <-- NEW
    2. AWG’s 2011-11-08 DRAFT-A OSEHRA/VistA Product Definition for “Gold Build” and certification is posted at http://www.osehra.org/node/47/content/documents. Please provide feedback.
      1. Spread sheet of VistA Documentation Library (VDL) modules has the following columns
        • Module – Name of module in VDL
        • Version in build
        • Class – [1, 2, 3, other]
        • Applicable patches
        • Applicable ICRs
        • Applicable Namespaces
        • Comment – mitigating circumstances
      2. ACTION (Peter Li): add current module version to OSEHR “Product Definition” spreadsheet.
    3. OSEHRA will start a weekly teleconference to discuss the current set of OSEHRA software development tools on Wednesday, November 16 from 3:30pm to 4:30pm EST. This first meeting will provide an introduction to the many software development tools that are now available for VistA/M developers from the www.osehra.org website. This includes OSEHRA’s:
  1. ISSUE: definition between “package” and “module”
    • DISCUSSION: A VDL package is a group of information resulting from a project, which may include one or more of the following:  module documentation, patch documentation, namespace/global or file documentation. A module is a set of routines; modules may be categorized as parents or children.
  2. ACTION: separate teleconference among Julie Harvey (VA Product Development, Director, Product Assessment Competency Division, Bay Pines Product Development Center), Peter Li  (OSEHRA System Architecture lead) and Afsin Ustundag (Ray Group International VistA refactoring lead) to discuss remaining undocumented modules, the OSEHRA Build definition, Interface Control Agreements (ICRs) and the VA database (official list) of Name-spaces, File-spaces, Modules and Routines and any other remaining. All results of the discussion will be brought back to the OSEHRA AWG.
    • ACTION (Julie Harvey): verify and validate content of OSEHR “Product Definition” spreadsheet.
  3. Review Open Issues: The following was deferred till telecom with Julia Harvey
    1. HELP NEEDED: see list of “open” undocumented modules below; where are these documented?
  4. Review iEHR SDK - Software Development Kit’s Interoperable EHR (iEHR)
    1. Conceptual Architecture slides 80+ will be reviewed and updated.
    2. REQUESTED ACTION: review iEHR SDK Conceptual Architecture and post suggested improvements in discussion.
  5. REQUEST (Dr Mike Lincoln, VA): review OSEHRA charter and organization at future AWG telecom.
  6. NEXT STEP: Begin EHR Services Platform (ESP) Implementation Guide (IG)


Undocumented VistA modules   Status: 18 Open

  2. Administrative Data Repository   Status: Closed
  3. Allergy Tracking System   Status: Closed
  4. BAR CODE MED ADMIN  Status: Closed
  5. CERMe-Care Enhance Review Manager Enterprise   Status: Closed
  6. CIRN-Clinical Information Resources Network   Status: Closed
  7. CPRS: GUI-Graphical User Interface   Status: Closed
  8. CPT/HCPCS CODES  Status: Closed
  9. Dietetics   Status: Closed
  10. Discharge Summary   Status: Closed
  11. Education Tracking   Status: Open
  12. HEPC Registry   Status: Open
  13. HIV Registry   Status: Open
  14. HealthVet Desktop   Status: Closed
  15. Hemodialysis   Status: Closed
  16. Lab Service   Status: Closed
  17. MAS-Medical Administration Service   Status: Open
  18. NDBI-National Database Integration   Status: Open
  19. OE/RR-Order Entry/ Results Reporting   Status: Closed
  20. PXPT-PCE Patient/IHS Subset   Status: Open
  21. EA_Copied_Elements Status: Closed
  22. Patient Service Lookup   Status: Open
  23. Person Service Construct   Status: Open
  24. Pharmacy   Status: Open
  25. Pharmacy:  Electronic Claims Management Engine (ECME)   Status: Closed
  26. Progress Notes   Status: Closed
  27. Registration   Status: Closed
  28. Registration, Enrollment, and Eligibility Systems   Status: Closed
  29. SDS-Standard Data Service   Status: Open
  30. Stay Manager   Status: Open
  31. Text Generator   Status: Open
  32. VA Intranet   Status: Closed
  33. ICD9-CM  Status: Open
  34. Medical Domain Web Service  Status: Open
  35. Utilization Management Rollup  Status: Open
  36. Communications Service Library  Status: Open
  37. Fee Basis Claims System (FBCS)  Status: Open
  38. CORBA Services  Status: Open