1. ISO 21090 Datatypes Approved by Enterprise Composite Architecture team (eCAT) on July 7, 2009 Guidelines for use for CBIIT funded projects

2. Agenda Motivation Background Guidelines Implementation Plan Risks and Mitigation Questions

3. Motivation According to ECCF guidelines, requirement that in order to achieve Computable Semantic Interoperability (CSI), attributes of the static information model must be bound to robust data type specification ISO 21090 data types provide a harmonized set of data type definitions for representing and exchanging healthcare related information Developed and reviewed by large scale international team of experts and supported by standards organization such as HL7 and ISO Known to be under consideration by Canada Health Infoway

4. Process Used in Developing Guidelines Conducted meetings with following stakeholders COPPA technical team leads who are currently implementing some of the data types Members of the HL7 organization that have been involved in the development of the standards Members of the CBIIT semantic operations team that are currently working with the COPPA team and participating in the standards bodies Members of the SAIC-F team that are responsible for technical management of caBIG funded software development effort eCAT team

5. Guidelines Use of ISO 21090 data types is required for CBIIT-funded projects. Every project will be required to utilize the CBIIT “localization” of the data type. Any CBIIT-funded project wishing an exception will be required to receive a waiver from the eCAT (Enterprise Composite Architecture Team) (discussed in slide 9) There are no current standard open source implementations available to the project teams outside CBIIT, at this time. CBIIT (via eCAT) has determined to validate the standards by supporting pilot projects. When a project which identifies a need for an ISO 21090 data type that does not yet have a CBIIT localization, that team will identify this need to the eCAT. The eCAT will identify a pilot project to define the CBIIT localization for the CBIIT data type.

6. Guidelines (Continued) Projects considering using data types that are not in the “approved” list are required to contact ISO Project Manager to determine if there is existing “pilot” effort The project team is expected to coordinate with existing pilot effort and ensure that the project will be able to leverage the data types developed by the pilot at appropriate time defined in the project plan If there is no existing pilot activity, the ISO Project Manager will be required to propose pilot project to the eCAT. The eCAT will recommend whether to launch a new pilot project or expand the scope of existing pilot C-team will take appropriate funding decision in a timely manner based on eCAT recommendation and project teams will plan accordingly

7. Guidelines (Continued) A list of “approved” ISO 21090 data types will be maintained by CBIIT and implementation package. Approximately 1/3 of the 80 data types have localizations. An overall project manager (called as “ISO Project Manager” or “ISO Czar”) will maintain the content and be primary point of contact for project teams

8. Guidelines (Continued) The data types are required only at the “public interfaces” (or public APIs) of the analytical services The data types are not required for any internal data structures or persistence tiers

9. Guidelines (Continued) If a project cannot use the existing implementation of “approved” data types, the project team will be required to coordinate with the ISO Project Manager and provide reasons, including specific enhancements needed before using the data types The govt. lead for the project and the ISO Project Manager will be required to jointly present alternatives to the eCAT on future integration (including addressing any needed enhancements)

10. Steps and Timelines for Implementing the Guidelines It is understood that these guidelines could potentially be disruptive to projects that are either underway or in the pipeline Contractual Constraints Product schedules, Etc There is also need to develop appropriate organization (ISO Project Manager), implementation guidelines, and communication mechanism The phase-in period ends March 1, 2010 The eCAT will review the policy about 12 months after the policy is in place, to determine if changes needed in the guidelines Review period: March, 2011

11. Down the road Lack of Tool Support Integrating the ISO 21090 data types in projects may be time consuming and require additional tools or enhancements to existing tools, such as Software Development Kit, caCORE Workbench, caAdapter and Introduce Toolkit. We have been working with the Core team to determine an effective way to store the ISO 21090 data types in the ISO 11179 structure. Other efforts to improve our tools to better automate they system will begin around March or April.

12. Useful Links The approved guidelines are at the eCAT wiki site https://wiki.nci.nih.gov/display/ISO21090/ISO+21090+Wiki+Home+Page The ISO 21090 standard can be found at http://gforge.hl7.org/svn/hl7v3/trunk/dt/iso/index.htm The COPPA ISO 21090 PIM can be found at https://gforge.nci.nih.gov/svnroot/coppa/trunk/documents/analysis_and_design/

13. Discussion