The Integrated Data Repository (IDR) provides the technical and organizational framework for various health-related applications. The IDR provides the core structure for the all EPHRS Applications and utilizes open health information technology architecture. This model provides protection of privacy, maintenance of confidentiality for individuals, and security for information included in the registry.
IDR establishes a core of individual patient information which enables access of data to authorized personnel and the integration of immunization services with other public health organizations.
The SHS development model utilizes an open architecture that provides the IDR with the ability to be a modular and scalable application foundation. Utilizing the SHS development model the applications designers and builders may focus on each component layer and utilize the best methodology. The development model allows for the segregation of the four basic system technology layers. The layer segregation allows the IDE to expand and evolve as EPHRS requirements change.
Presentation Layer - This includes the system security components, browser interface, and system integration modules. Security enhancements, additional Internet browser support, or external system integration may be accomplished without adversely effecting the existing application processing logic.
Functionality Layer - Segregation of this layer allows for the integration of additional applications into the IDR without disrupting existing applications or workflow processes. This segregation of the functional layer allows for the modular expansion of the IDR as additional requirement of functions becomes necessary.
Rules Layer - This layer contains the decision rules that are applied to the registry data and are segregated from the other components of the architecture. A change within the rules layer ensures that all applications utilize the most current information available.
Data Layer - Expansion of the data layer repository may be accomplished without impacting existing application processing. Database performance, tuning, and distribution may be performed without adversely effecting the applications that are accessing the data. It may be centralized or distributed without forcing application logic modification. This segregation of the data allows for a flexible and scalable data repository independent of the application functions.