Logica was created with a vision of helping to transform the health information technology (HIT) landscape by leveraging a provider-led not-for-profit community advancing open platforms, open systems, open standards, and open content. Having recognized multiple barriers adversely affecting the unfettered sharing of health information and inability to seamlessly provide care across care settings and institutions, the Logica benefactors started this consortium to attract a diverse community and ultimately a wide variety of initiatives and projects.
Logica as a community seeks to address a number of significant business challenges faced by health provider organizations, and the health community writ large, such as:
- Inherent limitations within the HIT marketplace to provide seamless solutions
- Inconsistencies among widely adopted HIT standards
- Insufficient richness in the expression of clinical detail, curtailing the ability to provide for computer-assisted clinical decision support
- Competing technology stacks, resulting in additional challenges when integrating systems or sharing between health systems
- Lack of a common health platform, limiting third party innovation
To clarify the direction of the HPSC community and align key activities, the HSPC Interoperability Roadmap was developed. This articulates the target-state vision for where HSPC believes the HIT industry should go, and the path toward attaining it. This is detailed in four phases, identifying a set of realized capabilities, the highlights of which appear in Table 1, following.
|Capabilities Delivered (Highlights)||Phase 1||Phase 2||Phase 3||Phase 4||Industry Benefit|
|Basic terminology authoring||X|
|Enable readiness assessments||X|
|Publish foundational knowledge content||X|
|Specify core platform elements||X|
|Support for Knowledge Lifecycle||X|
|Align industry semantic models||X|
|Release CDS content/ knowledge||X|
|Enhance UI Experience||X|
|Share clinical processes/workflow||X|
|Cultivate a knowledge ecosystem||X|
|Enhanced computable model execution||X|
|Security infrastructure services||X|
|Enable shared analytics services||X|
|Fully realized content ecosystem||X|
|Thriving application ecosystem||X|
|Assessment & Compliance||X|
|Platform and product certification||X|
|De-facto interoperable Logica solutions||X|
Document Organization. The Logica Roadmap has three principal sections, allowing a broad diverse set of stakeholders to effectively interact with the content. It merits mention that much of the content of the Roadmap is actually repeated and available in each of the sections below, but they are organized differently and thus serve different audiences and purposes. The core sections of the document are:
- The Transition Map, a visual description of how we move from the present state of the industry toward our community vision (Section 2)
- A Phased View(Section 3), which uses a time-oriented perspective to describe capabilities under development and when they will be available for use
- A Functional View(Section 4), which considers several core areas to illustrate the progression along topical lines, building maturity of capabilities (e.g., Business View, Infrastructure, Knowledge, etc.) and advancement of each
Core Content. At the heart of the Logica Roadmap are the three sections identified above. A vignette of each principal section of the document follows. In addition to these core sections, the Roadmap contains instructions how to most effectively read and navigate the document, characterizes intended stakeholder communities and benefits that can be achieved, and known gaps and next steps.
The Transition Map comprises a set of segments to visually represent the core focal areas around which Logica is organizing its activities. There are three segments (Content, Context, and Platform) that are each divided into more granular “swim-lanes”, with topics such as Business, Information, Knowledge, Security, Software, etc). Also depicted are the phases of progress, the key capabilities realized, and specific deliverables and milestones.
The Phased View orients the Roadmap by time, detailing key activities that are underway and the “packaging” of those capabilities in terms of realized market capability. The intent of this phased view is to demonstrate the incremental achievement of new interoperability capability, and the realization of platform components and enabling tools for use by the Logica community and the HIT community writ large.
The Functional View provides specific detail about each of the milestones identified on the Roadmap, explaining their purpose, nature of the product or activity, known dependencies, and descriptive information. Note that out-year milestones are more notional and have less detail than activities presently underway. It is from this functional view, however, that the progression and maturation of capabilities is described and detailed.
Roadmap Use. The Logica Roadmap will serve several purposes and objectives, depending upon your individual role and the nature of engagement with the Logica community. It merits mention that most
|It is expected that the Roadmap has a larger role to fill, particularly in assisting like-minded community contributors to determine where and how they might help advance the needs of industry.|
stakeholders will likely interact with only portions of the Roadmap in any given context. For example, a specific Logica project will likely produce one or several products that are identified as Roadmap milestones, but will also have other milestones that do not appear. That is to be expected. Similarly, that same project will likely have dependencies on other Milestones produced by other efforts. The roadmap provides a unified view, showing how different parts of the ecosystem fit together to build the greater whole.
The Transition Map is the focal component of the Logica Roadmap. It was created through an iterative process of brainstorming, analysis, and modeling, with each step being assessed for fitness-for-purpose based upon the intended goal of articulating the areas of priority for Logica and the
Current State (“1” on the figure). The current state appears on the T-Map as a box in the lower left corner. It contains 5-7 bullet points describing the state of the industry as it stands today. Specifically, the Current State describes today’s interoperability challenges and common practices in HIT.
Future State (“2” on the figure). The future state appears on the T-Map as a box in the upper right corner, describing our aspirational future reality: the world as we would like it to be. Specifically, the Future State is based upon Logica’s Mission and Goals, community input, active and planned work, and strategic initiatives.
Segments and Swim-lanes (“3” on the figure). Reflected on the diagram as the “sunburst” from the upper right corner, the complex domain has been divided into segments and then again into swim-lanes. Each segment represents a specific perspective by exclusively focusing on a defined high-level theme, and is characterized by a principal problem statement appearing along the boundary of each swim-lane. The swim-lane construct simplifies these complexities by “telling the story” one perspective at a time, noting that interdependencies exist among them.
Phases (“4” on the figure). Appearing as radial arcs, the phases within the T-Map represent time, with the outermost band representing the present day and the innermost reflecting the target state. Note that the phases transcend the swim-lanes, and in fact unify activities and milestones.
The phases represent “major deliverables” and can be anecdotally considered Logica 1.0, 2.0, 3.0, etc.
Milestones (“5” on the figure). Within each swim-lane are identified a number of milestones, each of which indicates an objective, measurable point indicating the completion of an activity within that lane. The milestones represent the path from the “As Is” to the “Future State”
Reading the Diagram. The heart of this roadmap document is the central graphic – the “Transition Map”(abbreviated as T-Map) – that depicts an “at a glance” a visualization of the major areas of interest and corresponding milestones related to those areas.
These swim-lanes are not categories and are not mutually exclusive. They are perspectives, looking at the problem space from a particular point-of-view, and highlighting milestones and considerations reflected from that point of view. Architecturally speaking, this is a “separation of concerns”, where each swim-lane represents a different dimension of this health information technology landscape. For this reason, it is common for one project or activity to have milestones in multiple swim-lanes, and that occurs in this Logica T-Map.
Please reference the “T-Map Described” callout box for a description of each element of the diagram. The 2018 Logica T-Map follows. Note that the swim-lane/segment view does not reflect one particular project or product, rather it provides the cross-section of milestones affecting multiple Logica efforts, illustrating the critical path to achieving our future vision.