Professional Documents
Culture Documents
Bpe 2
Bpe 2
As-Is
2
"As-Is" process involves mapping out the existing software deployment processes at ABC
Healthcare Solutions. According to the BPMN, 2 main problems and their possible reasons
were identified in the As-Is Process:
1)Delays in Releases
Reason: lack of thorough risk assessment and mitigation. The existing processes lack a
comprehensive risk assessment and risk mitigation strategy, leading to potential unexpected
challenges during development, testing, and deployment. This can be the reason of
insufficient release planning, resulting in delays in releases.
SIPOC
3
Supplier
Software developers, quality assurance teams, project managers, and support staff.
Inputs
1. Software updates
New features, bug fixes, and enhancements developed by the software
development team.
2. Client requirements
Specific needs and preferences communicated by the healthcare organizations
or clients utilizing the EHR systems.
3. Test data
Data sets used for testing the software updates and deployments to ensure
quality and compatibility.
4. Deployment environment
Information about the infrastructure, servers, and network configurations
where the EHR systems will be deployed.
5. Documentation
Instructions, manuals, and technical documentation related to the software
deployment process.
Process
1. Design
Write the design
Document the design specifications and architecture for the software
updates.
Create the test plan
Develop a plan for testing the software changes to ensure they meet the
requirements.
Perform an impact analysis
Assess the potential effects of the proposed changes on the existing
system and stakeholders.
2. Build
Develop software
Implement the changes and new features as per the design
specifications.
Write documentation
Create user manuals, release notes, and other documentation to
accompany the software updates.
Create test specifications
Define the test cases and scenarios to validate the functionality of the
software changes.
4
3. Test
Testing
Write test reports
Document the results of the testing process.
Release software
Deploy the software updates to the production environment for
implementation.
4. Implement
Acceptance testing
Conduct testing with end-users to ensure the software meets their
requirements and expectations.
Implementation in Production
Deploy the software updates to the live environment, following best
practices and minimizing downtime.
Outputs
1. Software upgrades
2. Customer satisfaction
Clients have expressed gratitude for the effectiveness and quality of the
software upgrades and deployment.
Customer
The hospitals, clinics, and healthcare organizations that use the EHR systems created
by ABC Healthcare Solutions are the clients of the software deployment and upgrade
process. They obtain the installed software upgrades and take use of the enhanced
functionality.
Workflow
● Internal Project Managers. Who prioritize and allocate resources based on internal
initiatives and strategic objectives.
● External Clients. Who submit requests based on their specific needs, preferences, or
challenges encountered while using the EHR systems.
5
Value-Added (VA) Activities
● Creating improvements and new features in response to customer needs.
● Testing software to make sure it satisfies customer requirements and quality
standards.
● Applying upgrades and modifications that immediately increase the EHR software's
usability or functioning from the viewpoint of the user.
6
Observations and Insights
7
To-Be
8
“To-Be” process involves mapping out future activities that ABC Healthcare Solutions
plans to do, considering existing problems and proposing possible solutions. As identified
from the “As-Is” process, there were 2 main problems: delays in releases and difficulties
incurred by clients during the implementation phase. The above BPMN proposes possible
solutions to these issues:
Roadmap
In the case of software implementation in healthcare, such a methodology becomes critical as
it addresses the specific requirements of this sector such as data privacy, regulatory
compliance, etc.
9
This roadmap summarizes the milestones that form the basis of implementation, as well as
the statuses of implementation and deadlines.
10