Information Architecture Model Analysis Sample Clauses

Information Architecture Model Analysis. We evaluated the pros and cons of architectural models as they applied to the ALTCDSS. This assessment had a major role in determining the best fit for our project objectives. The image below illustrates the inverse dynamic between the business and the data management component in each IA model. Image Source: Compact Below are the pros, and cons of each model, from a system perspective. Those starred (*) contain the considerations of most concern for the ALTCDSS. Centralized- Recommended Pros Cons Highest-level of control High upfront investment in central resources Single Data Source- one stop shop* Strong central coordination is required. The central database cluster needs to be carefully managed and maintained for this system to work. Offers the best level of data management; well defined data fields through governance, to include the addition or change in existing fields. More risk on the central location, if other centers do not participate. * Economies of scale can be introduced by using large-scale central resources, if appropriate investments are made. Timeliness. Data submissions from participating systems may lag, resulting in inaccurate consolidated records at query time. Typically, the querying system’s response to a data request is quicker than other models because the data is centrally maintained and consolidated Likely expensive option to implement, not only technically, but organizationally No need for local experts to receive customized reporting; or information * Less flexibility for other centers * Better expertise in managing central resources due to their scale and class of products used All data must be abstracted into the UI for the central system ie. no possibility for sourcing data from distributed systems. More structured solution * Easier to enforce data governance * Less costs to external centers: could promote their buy-in * Successful use by subject-related registries (i.e. NSQIP, SRTR) * Hybrid- Not Recommended Pros Cons Gives the collaborating centers their own autonomy Difficult to initiate without investment, and considerable IT resources, at each location * Shares the responsibility of the system, across centers * Shares the responsibility of the system, across centers; less control * Data is always current. Models, standards and profiles are still being defined. Not a widely- used model, to compare or evaluate against * Any EHR system can be connected to any other, but assumes common interface standards. Harder to employ...