To prepare VistA to serve as the evolution of the iEHR, VistA must be updated to modernize the way in which other products connect to it. By creating accessible services out of key pieces of VistA functionality, VA will create entry points for other products to connect to VistA. These services must be compliant with VA Office of Information and Technology (OI&T) Enterprise Architecture, be accessible through an enterprise Messaging Infrastructure (eMI) formerly the Enterprise Service Bus (ESB) and secured using Identity and Access Management (IAM) Services.
The VistA API 2.0 project is being executed using Agile practices and methods. As is typical in Agile projects, a project backlog will be developed and maintained for the duration of the project. Items on the backlog will be prioritized periodically and the top priority items will be selected for the upcoming sprint.
The current backlog consists of several domains, each of which will require API services to be specified and developed:
• Immunization Information
• Clinical Warnings and Directives
• Allergies Adverse Reaction Tracking
• Problem List
• Vitals
• Imaging