Data Flow Diagrams
The existing system data flow identifies users interact with the new system. It also highlights the relationship of the legacy data to the new patient record database. Appendix F contains the source file for the diagrams below.
The legacy conversion data flow identifies how legacy records will be converted and accessible to the new system. The IT technician will gather paper records for patients based on our prioritization. The records will be scanned, coded and formatted for accessibility. Any errors will be identified and re-processed.
Process Model A process model is a systematic format for planning, organizing, and running an information technology (IT) development project. It is a description of …show more content…
The number of iterations is determined by the partitioning of the design. Iterations should be planned for durations of one work-week for each. One-week increments and the number of developers available to work on the project determine the number of features that can be included in each Incremental-build. This in turn determines the overall schedule.
Figure 2: An Incremental-Build Process Model Example
(Fairley, 2011, p. 61) Figure 2 illustrates another advantage of the Incremental-build process model, namely the ability to gracefully make trade-offs among product features, resources, and the delivery schedule. If, for example, the compiler is not ready for delivery as scheduled at the end of six months, a choice can be made between delivering a first version of the compiler without the optimizer, or extending the schedule to allow successful completion of Project Pluto. Because of the frequent demo milestones, early warning of slippage in the delivery schedule is provided and offers the option to add more or better developers to the project to meet the delivery date. Because of the detailed history of progress, it should be possible to accurately estimate the amount of time needed …show more content…
The key assessment was for a tool and process to convert legacy documents.
Legacy data conversion application
Project Pluto team members identified key architecture and application design alternatives when selecting the legacy data conversion application. There were two architecture options analyzed and three application design alternatives analyzed.
The two architecture options were on premise hosted and on demand hosted. On premise means the application would be physically hosted within the MHCS network on internal servers. On demand means that the application would be externally hosted, such as Software as a Service (SaaS) solution is.
The three main legacy conversion alternatives included manual data entry, EHRStatic-new application, and functionality within the existing Systemedx application. The following matrix shows the variants of both these dimensions.
Location/App Manual data entry EHRStatic Systemedx Clinical Navigator 2013.12
On Premise N/A
The existing system data flow identifies users interact with the new system. It also highlights the relationship of the legacy data to the new patient record database. Appendix F contains the source file for the diagrams below.
The legacy conversion data flow identifies how legacy records will be converted and accessible to the new system. The IT technician will gather paper records for patients based on our prioritization. The records will be scanned, coded and formatted for accessibility. Any errors will be identified and re-processed.
Process Model A process model is a systematic format for planning, organizing, and running an information technology (IT) development project. It is a description of …show more content…
The number of iterations is determined by the partitioning of the design. Iterations should be planned for durations of one work-week for each. One-week increments and the number of developers available to work on the project determine the number of features that can be included in each Incremental-build. This in turn determines the overall schedule.
Figure 2: An Incremental-Build Process Model Example
(Fairley, 2011, p. 61) Figure 2 illustrates another advantage of the Incremental-build process model, namely the ability to gracefully make trade-offs among product features, resources, and the delivery schedule. If, for example, the compiler is not ready for delivery as scheduled at the end of six months, a choice can be made between delivering a first version of the compiler without the optimizer, or extending the schedule to allow successful completion of Project Pluto. Because of the frequent demo milestones, early warning of slippage in the delivery schedule is provided and offers the option to add more or better developers to the project to meet the delivery date. Because of the detailed history of progress, it should be possible to accurately estimate the amount of time needed …show more content…
The key assessment was for a tool and process to convert legacy documents.
Legacy data conversion application
Project Pluto team members identified key architecture and application design alternatives when selecting the legacy data conversion application. There were two architecture options analyzed and three application design alternatives analyzed.
The two architecture options were on premise hosted and on demand hosted. On premise means the application would be physically hosted within the MHCS network on internal servers. On demand means that the application would be externally hosted, such as Software as a Service (SaaS) solution is.
The three main legacy conversion alternatives included manual data entry, EHRStatic-new application, and functionality within the existing Systemedx application. The following matrix shows the variants of both these dimensions.
Location/App Manual data entry EHRStatic Systemedx Clinical Navigator 2013.12
On Premise N/A