Objectives ( for this presentation ) :

1. CBIIT (NCI) Services Aware Interoperability Framework (SAIF) Implementation Guide:Information FrameworkDraft as of 20 January 2011*Status update and salient topics for review and discussion [VCDE Authors] Mukesh Sharma, Grace Stafford and Stuart Turner [Architecture Author] Jim McCusker[SAIF IG Collaborators] Raghu Chintalapati and Cecil Lynch[Government Sponsor] Sherri de Coronado[XC WS Oversight] Brian Davis and Riki Ohira SAIF Information Framework Working Group (NCI Wiki): https://wiki.nci.nih.gov/x/dLr9AQ • Presented at the caBIG (NCI) VCDE Workspace teleconference 20 January 2011 CBIIT (NCI) SAIF Information Framework Implementation Guide - Status update for review & discussion | 20 January 2011

2. Objectives (for this presentation): Update regarding the status of the SAIF Information Framework IG (draft as of 20 January 2011) Approach: less abstract, more concrete (selected excerpts) Caveats: We missed publication of interim draft for 15 January 2011 due to holidays and conference/travel schedules (mea culpa!) Issues that need to be resolved before publication: Breadth of domain perspectives too narrow. Content (to-date) derived largely from caCIS development and HL7‘s Development Framework therefore intrinsically HL7-centric. Inclusion of life sciences examples are on the horizon. Detail in draft is coarser than intended for final version. Integration of more precise content via a prescriptive style is being developed now. Examples: Detail regarding traceability Complimentary integrative images to better conceptualize text are pending as well. CBIIT (NCI) SAIF Information Framework Implementation Guide - Status update for review & discussion | 20 January 2011

3. Introduction (background) “..detail the artifact components of each of the conformance layers” "..information models with data type, classes, relationships,defined entry points and terminology bindings" "semantic profiles" “Although defined in the Behavioral Framework, we will briefly discuss the semantics of relevant sequence diagrams" “Relevant standards (e.g. vocabulary, identifiers, and DAM) Other "..ensure this alignment of business requirements..determine the traceability from the concrete end software product to those abstract business requirements that served as the blueprint for the final software." "..ensure a lossless transform of information from the conceptualization of the analysis artifacts to the serialization of those artifacts" "..will include a set of examples drawn from the life sciences and the clinical domain within the realm of cancer research and care“ CBIIT (NCI) SAIF Information Framework Implementation Guide - Status update for review & discussion | 20 January 2011

4. Assumptions SAIF is inherently standards-based: this section outlines standards and best practices. “To define (or redefine) a select group of essential binding technologies." Objective is to set the stage regarding shifts in technologies as well as those that may be new for those working in caBIG 1.0 as well as those stepping into caBIG 2.0 anew. Semantic Service Oriented Architecture (SSOA) Unified Modeling Language (UML) ≥ 2.1 HL7 RIM Semantics "Examples derived from both life and clinical sciences" Molecular Analysis In Vivo Imaging (e.g. AIM) TBPT Healthcare Complex Data Types (ISO 21090) NCI Vocabulary Services Others within scope and context (e.g. RMODP and OMG's MDA, etc.) CBIIT (NCI) SAIF Information Framework Implementation Guide - Status update for review & discussion | 20 January 2011

5. Computationally Independent Model (CIM) "All artifacts in this level concentrate on expressing the business requirements provided by subject matter experts (SME) as well as perspectives related to business analysts (BA)" SME - external facing view; BA - internal facing view Concept maps "approachable method..intuitive and require minimal technological sophistication or training...easily created and edited by either SME's or BA's" Refined concept map (iterative) Business Analyst adjusts to better fit known domain vocabulary and knowledge organization for rendering into a set of UML diagrams Traceability: Concept Map → UML Model "[capture] each concept map node in one or more UML classes...[capture] all concept map edges as UML relations between classes“ CBIIT (NCI) SAIF Information Framework Implementation Guide - Status update for review & discussion | 20 January 2011

6. Computationally Independent Model (continued) UML Business Conceptual Class Models "UML diagrams are constructed by the BA but at the conceptual level still use the nomenclature that is friendly to the SME." remains the "external facing" component "BA refines the model and splits classes into more granular class definitions" "until eventually a class can be fully defined by only the necessary and sufficient attributes that provide the entire context for that class and does not overlap with the context of another class in the model." “stage where "business analyst should reference any domain analysis models that exist" "UML..models introduce the ability to add data typing for each attribute" "reconciling the domain reflected by the SME with a DAM is called harmonization...may well be iterative" "NCI we use the ISO-21090 unconstrained data types" "the SME and the BA are not referencing any particular RIM, though it is implied that all of the constructs used will be covered by the NCI's designated RIM source" image of core RIM classes CBIIT (NCI) SAIF Information Framework Implementation Guide - Status update for review & discussion | 20 January 2011

7. Computationally Independent Model (continued) Domain Analysis Models SME and BA rarely start with a DAM SAIF IF IG document currently references only BRIDG and LS DAM Example person class (image) "elucidate[s] why the last layer of the CIM artifact is not expressed in standard UML tooling and instead uses the HL7 RMIM designer tool to be able to express these domain terminology constraints" "The detail provided by the additional attributes of the data type are inappropriate at the CIM level because it implies that requirements for the terminology value sets at the implementation level is known, which is never the case at the DAM level since many implementations can be derived from a DAM" Traceability: DAM → RMIM "Traceability between the domain analysis model and the domain message information model (DMIM) is at the level of class, attribute, and data type and includes the relationships between the classes of the mode" DAM classes: one to many mapping to DMIM (classes and relationships) Example (Figure) _ "LS DAM Used in Molecular Annotation“ CBIIT (NCI) SAIF Information Framework Implementation Guide - Status update for review & discussion | 20 January 2011

8. Computationally Independent Model (continued) Design Information Model (DIM) or DMIM (to reconcile terminology) Lowest level of the CIM At DMIM, no longer model in standard UML to bind vocabulary to the model and constrain data type flavors at this level Example of Laboratory DMIM Constrained models can only be derived from a single DMIM Traceability: DMIM → RMIM The next level of information model is at the PIM level and the artifact is called a Refined Message Information Model or RMIM. The RMIM is directly traceable to the DMIM through classes, attributes, data types, relations and vocabulary domains. The RMIM may constrain the attributes and classes but it cannot add any new elements to the new model. Where classes are persisted to the RMIM from the DMIM, the relations must remain the same between classes. The terminology bindings in the RMIM must be from the same domain as specified in the DMIM. CBIIT (NCI) SAIF Information Framework Implementation Guide - Status update for review & discussion | 20 January 2011

9. Platform Independent Model (PIM) “Includes components of HL7's HDF Serializable Information Model (SIM), including RMIM, CMET, ISO 21090 and vocabulary concept domains” “DMIM artifact from the CIM (above) is a shared artifact between the CIM and PIM” (bridges these two layers) “Purpose of the PIM is to provide a translation of the lowest level CIM artifact (the DMIM) to a logical information model for a specific payload structure” PIM is a concrete model — can be serialized to a PSM model artifact Data types fixed to ISO 21090 (unconstrained) “Information models have corresponding MIF [HL7 Model Interchange Format] representations” Terminology can be refined to a more granular level than in the CIM CBIIT (NCI) SAIF Information Framework Implementation Guide - Status update for review & discussion | 20 January 2011

10. Platform Independent Model (continued) RMIM - Refined Message Information Model “Represents the static information model refinement of a portion of a single DMIM” “Does not span more than one DMIM” “Does not represent full content of a DMIM” “Contains one or more CMET's” Single entry point “RMIM thus formed by constraint and refinement of the DMIM will serve as the static information structure for a single service operation parameter payload at the PSM layer” CBIIT (NCI) SAIF Information Framework Implementation Guide - Status update for review & discussion | 20 January 2011

11. Platform Independent Model (continued) Common Message Element Type (CMET) “common, useful and reusable set of concepts” or “message type fragment” “used across multiple sub-domains within a healthcare model” “act as a reference to a model from within an RMIM or another CMET” “part of the traceability package of the RMIM → DMIM” “not constrainable without the creation of a unique CMET” CBIIT (NCI) SAIF Information Framework Implementation Guide - Status update for review & discussion | 20 January 2011

12. Platform Independent Model (continued) ISO 21090 data types "In this layer (PIM), there is no consideration of how the complex healthcare data types will be serialized to the primitive data types of a specific language representation" "may be a payload for an operation parameter of a service“ CBIIT (NCI) SAIF Information Framework Implementation Guide - Status update for review & discussion | 20 January 2011

13. Platform Independent Model (continued) Vocabulary Binding Binding in one of three ways 1)"The concept domain identified in the DMIM may be reused without further refinement." 2) "A sub-domain of the DMIM concept domain may be defined (a refinement) which may be declared a value set" 3) "A specific code that is fixed for the attribute." Concept domain (brief description) Value set[s] (brief description, including HL7 definition) "It is only at the PSM layer that value set binding can reliably occur since implementation considerations define the terminology required at the interface in almost all cases." Traceability: RMIM classes, attributes and data types should be traceable to the DMIM in all cases RMIM is a constraint on the DMIM DMIM will have concept domains that are further refined in scope in the RMIM but in all cases will have concepts restricted to those that are part of the set of concepts contained in the concept domain bound to the attribute in the DMIM. CBIIT (NCI) SAIF Information Framework Implementation Guide - Status update for review & discussion | 20 January 2011

14. Platform Specific Model (PSM) NB: This section is still very much at the inception phase NCI SAIF assumptions "SOAP-based web service using an XML payload" "ISO data types will not be localized for external facing NCI services." "It is conceivable however that certain services will be used in a more limited scope and that localization of the data types may be negotiated between a limited group for a specialized purpose. It is at the PSM layer that this localization of data types would occur." "The information model for the data types in the PSM layer is the serialization described by the XML standard using XSD primitive data types." RMIM XSD The payload of each service operation parameter is either an RMIM or an ISO 21090 data type Example XSD: PatientPersonInformational COCT_MT50007US RMIM Vocabulary Value Sets "Vocabulary is constrained in the PSM layer by the conversion of vocabulary domains identified in the PIM RMIM to specific value sets.“ CBIIT (NCI) SAIF Information Framework Implementation Guide - Status update for review & discussion | 20 January 2011

15. The SAIF Information Guide IG will have its first public release on the wiki very shortly. A PDF export of the current draft (including provisional images) and a hyperlink to the relevant wiki artifacts will be provided in context of this VCDE presentation (e.g. mailing list, archive) Thanks also to Ann Wiley as well as members of the Semantic Infrastructure Roadmap Group. The collaboration (research, review, disposition) with the SAIF IF IG workgroup has been effective and informative. Questions or Comments? CBIIT (NCI) SAIF Information Framework Implementation Guide - Status update for review & discussion | 20 January 2011