Amia now! session one

613 views
521 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
613
On SlideShare
0
From Embeds
0
Number of Embeds
14
Actions
Shares
0
Downloads
30
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Talking Points:Areas covered include but are not limited to: protocols, studies, study sites, organization and org roles, people and people roles, study subjects, study activities (e.g. subject enrollment, specimen collection, lab work, etc.) , products, study design, documents, regulatory artifacts
  • Amia now! session one

    1. 1. Standards Influenced Research Information Systems InteroperabilitySession One: Information Modeling<br />AbdulMalik Shakir, Information Management Strategist<br />City of Hope, Duarte, CA<br />
    2. 2. About Me<br />Abdul-Malik Shakir<br />Information Management Strategist with City of Hope<br />Principal Consultant with Shakir Consulting<br />HL7 Member since 1991<br />Co-Chair of the HL7 Education Workgroup<br />Member of the HL7: <br />Architectural Review Board<br />Public Health and Emergency Response Workgroup<br />Regulated Clinical Research Information Management Workgroup<br />Modeling and Methodology Workgroup<br />Member of the BRIDG Board of Directors since January 2010<br />Modeling Facilitator for CTR&R, SAP, STDM, and caEHR<br />May 2010<br />2<br />Standards Influenced Research Information Systems Interoperability<br />
    3. 3. Research Informatics Systems Engineering<br />May 2010<br />3<br />Standards Influenced Research Information Systems Interoperability<br />
    4. 4. Session Overview<br />Domain Analysis Modeling<br />The Value of Modeling<br />What is a Domain Analysis Model (DAM)<br />What is the Unified Modeling Language (UML)<br />Biomedical Research Integrated Domain Group (BRIDG – Domain Analysis Model)<br />HL7 Clinical Trail Registration & Results DAM<br />Requirements Gathering<br />BRIDG DAM Mapping<br />BRIDG Subset Definition<br />COH Semantic Interoperability Infrastructure<br />Metadata Services<br />Terminology Services<br />Ontology Services<br />Rule Services<br />May 2010<br />4<br />Standards Influenced Research Information Systems Interoperability<br />
    5. 5. Domain Analysis Modeling<br />PARTY IDENTIFICATION NUMBER<br />PARTY<br />PARTY ACTIVITY ROLE<br />Identification Number<br />Begin Date<br />Issuing Authority Name<br />End Date<br />Issue Begin Date<br />Role Code<br />Issue End Date<br />CASE DEFINITION<br />PARTY CASE DEFINITION ROLE<br />Type Code<br />Begin Date<br />Begin Date<br />Category Code<br />End Date<br />Description<br />Role Code<br />End Date<br />PATIENT COVERAGE<br />Name<br />Provider Code<br />PARTY CASE ROLE<br />Begin Date<br />End Date<br />Role Code<br />BILLING ACCOUNT<br />PARTY NOTIFICATION<br />CASE<br />Begin Date<br />Begin Date<br />End Date<br />Confirmation Method Code<br />PARTY TO PARTY ASSOCIATION<br />Notification Receiver Identification Number<br />Count<br />Notification Sender Identification Number<br />Begin Date<br />Count Type Code<br />Code<br />Detection Method Code<br />End Date<br />End Date<br />Identification Number<br />Transmission Mode Code<br />Status Code<br />Status Date<br />PUBLIC HEALTH NOTIFICATION<br />Begin Date<br />End Date<br />Identification Number<br />Reason Code<br />ORGANIZATION<br />INDIVIDUAL<br />Entity<br />Alias Name<br />Name<br />Name<br />Type<br />Type Code<br />Outbreak<br />Begin Date<br />DIAGNOSIS<br />End Date<br />PARTY CONDITION<br />Classification Scheme Code<br />Extent Code<br />Disease Code<br />Begin Date<br />Peak Date<br />Diagnosis Code<br />Description<br />Diagnosis Date<br />End Date<br />Source Code<br />Name<br />Source Text<br />Name Status Text<br />PERSON<br />NON PERSON LIVING ORGANISM<br />INFORMAL ORGANIZATION<br />Formal Organization<br />Status Date<br />OUTBREAK STATISTIC<br />Birth Date<br />Genus Name<br />Industry Code<br />Death Date<br />Species Name<br />Amount<br />Ethnicity Code<br />Category Code<br />PARTY LOCATION ROLE<br />Race Code<br />Type Code<br />Begin Date<br />Sex Code<br />End Date<br />Soundex Text<br />Role Code<br />Occupation Name<br />Status Code<br />Status Date<br />PARTY SPECIMEN ROLE<br />PERSON NAME<br />Begin Date<br />Degree Name<br />End Date<br />First Name<br />Role Code<br />Last Name<br />Middle Name<br />Prefix Name<br />Suffix Name<br />Type Code<br />PARTY VEHICLE ROLE<br />Begin Date<br />End Date<br />Role Code<br />VEHICLE<br />HEALTH RELATED ACTIVITY<br />Description<br />Begin Date Time<br />Name<br />Disposition Date Time<br />(Implication) Status Code<br />Disposition Description<br />Status Date<br />End Date<br />Type Code<br />Identification Number<br />Notification Indicator<br />Priority Code<br />Source Type Code<br />DISEASE ASSOCIATION<br />Type Code<br />LOCATION<br />Disease Code<br />Address<br />Disease Imported Code<br />Identification Number<br />Etiologic Status Code<br />Name<br />Etiologic Status Date<br />VEHICLE CONDITION<br />Setting Code<br />Exposure Begin Date<br />Type Code<br />Description<br />Exposure End Date<br />Description Status Code<br />Infection (or Illness) Type Code(s)<br />Status Date<br />SPECIMEN LOCATION<br />Begin Date<br />End Date<br />TEST REFERENCE TABLE<br />Method Code<br />Name<br />Samples Required Number<br />Samples Required Unit Code<br />SPECIMEN<br />Type Code<br />Collection Date<br />DISEASE CAUSING AGENT<br />Description<br />Agent Type Code<br />TEST<br />Identification Number<br />HEALTH STATUS INQUIRY<br />INTERVENTION<br />Agent Name<br />REFERRAL<br />Name<br />Amount<br />Amount<br />Referral Basis Code<br />Source Code<br />Amount Unit Code<br />Amount Number<br />Referral Type Name<br />Type Code<br />Begin Date<br />Amount Unit Code<br />Referral Acceptance Code<br />Description<br />Description<br />Description Code<br />Duration<br />ADDRESS<br />TELEPHONE<br />Duration<br />Duration Unit Code<br />Begin Date<br />Telephone Type Code<br />Duration Unit Code<br />Enrollment Code<br />City Name<br />Area Code<br />End Date<br />Enrollment Type Code<br />Country Name<br />Number<br />Live Births Number<br />Manufacturer Lot Number<br />County Name<br />Manufacturer Lot Number<br />Manufacturer Name<br />End Date<br />Manufacturer Name<br />Name<br />Postal Code<br />Reason Text<br />Route Code<br />TEST RESULT<br />CODE<br />Status Date<br />Result Date<br />Status Code<br />Amount<br />State Code<br />Code<br />Result Text<br />Status Date<br />Amount Unit Code<br />Street Address Text<br />Description<br />Status Code<br />Code<br />Type Code<br />Coding System Name<br />Status Date<br />Date<br />Travel Country Name<br />Description<br />Type Code<br />Description Code<br />May 2010<br />5<br />Standards Influenced Research Information Systems Interoperability<br />
    6. 6. Why Model<br />To aid in understanding relevant functions and information needs of a particular domain<br />To communicate the modeler’s understanding of the domain and allow that understanding to be assessed by others<br />To aid in reconciling multiple perspectives of a domain by combining varying perspectives into a single specification<br />To document a solution design (existing or planned) so that the design may be evaluated<br />May 2010<br />6<br />Standards Influenced Research Information Systems Interoperability<br />
    7. 7. Do you<br />play<br />football?<br />Yes, I do<br />play<br />football.<br />Revealing assumptions is an essential component of effective communication.<br />Data models are an effective means of documenting our assumptions<br />about a domain<br />Reveal Assumptions<br />May 2010<br />7<br />Standards Influenced Research Information Systems Interoperability<br />
    8. 8. Reduce Ambiguity<br />A<br />B<br />0..*<br />1<br />0..*<br />0..*<br />C<br />Modeling provides a language that allows us to unambiguously express our understanding and assumptions about the actions and information of interest in a particular domain<br />May 2010<br />8<br />Standards Influenced Research Information Systems Interoperability<br />
    9. 9. Reconcile Conflicts<br />X<br />B<br />A<br />B<br />0..*<br />0..*<br />1<br />1<br />0..*<br />0..*<br />0..*<br />0..*<br />C<br />C<br />Sharing models provides <br />an opportunity to identify and reconcile conflicts in our understanding <br />and to validate our assumptions.<br />May 2010<br />9<br />Standards Influenced Research Information Systems Interoperability<br />
    10. 10. Expand Understanding<br />A<br />B<br />A<br />B<br />0..*<br />1<br />0..*<br />0..*<br />0..*<br />1<br />0..*<br />0..*<br />C<br />D<br />Sharing models also provides <br />an opportunity to identify gaps in our understanding.<br />No one of individual has the complete view of domain of interest.<br />May 2010<br />10<br />Standards Influenced Research Information Systems Interoperability<br />
    11. 11. Consolidate Ideas<br />A<br />B<br />X<br />B<br />A<br />B<br />0..*<br />1<br />0..*<br />0..*<br />0..*<br />1<br />0..*<br />1<br />0..*<br />0..*<br />0..*<br />0..*<br />C<br />D<br />C<br />B<br />G<br />E<br />0..*<br />1<br />0..*<br />1<br />0..*<br />1<br />D<br />X<br />F<br />C<br />A<br />0..*<br />0..1<br />0..*<br />1<br />Model I<br />Model II<br />Model III<br />May 2010<br />11<br />Standards Influenced Research Information Systems Interoperability<br />
    12. 12. Value of Modeling<br />Reveal Assumptions<br />Reduce Ambiguity<br />Reconcile Conflicts<br />Expand Understanding<br />Consolidate Ideas<br />May 2010<br />12<br />Standards Influenced Research Information Systems Interoperability<br />
    13. 13. What is a Domain Analysis Model<br />A Domain Analysis Model (DAM) is a conceptual model used to depict the behavioral and static semantics of a domain of interest. <br />A DAM provides an opportunity for subject matter experts (SMEs) within a particular domain to integrate and harmonize their perspectives regarding the use cases, activities, and information needs of their shared domain. <br />A DAM is particularly useful when used in a domain with broad interests and a diverse population of SMEs.<br />13<br />May 2010<br />Standards Influenced Research Information Systems Interoperability<br />
    14. 14. Domain Analysis Model Use<br />A domain analysis model is used as reference material in development of information system interoperability specifications as well as design specifications of information system components <br />The DAM is a requirement specification and is the primary artifact from which information system design specifications are derived. <br />The preferred language for expression of a domain analysis model is UML.<br />14<br />May 2010<br />Standards Influenced Research Information Systems Interoperability<br />
    15. 15. Unified Modeling Language (UML)<br />UML is a standardized general-purpose modeling language in the field of software engineering. <br />UML is not a development method; however, it was designed to be compatible with the leading object-oriented software development methods. <br />UML includes a set of graphical notation techniques to create visual models of software-intensive systems. <br />15<br />May 2010<br />Standards Influenced Research Information Systems Interoperability<br />
    16. 16. UML Diagram Types<br />May 2010<br />16<br />Standards Influenced Research Information Systems Interoperability<br />
    17. 17. Domain Analysis Model Diagrams<br />17<br />May 2010<br />17<br />Standards Influenced Research Information Systems Interoperability<br />
    18. 18. Biomedical Research Integrated Domain Group<br />18<br />May 2010<br />Standards Influenced Research Information Systems Interoperability<br />
    19. 19. From Data Requirements to HL7 Message<br />May 2010<br />19<br />Standards Influenced Research Information Systems Interoperability<br />
    20. 20. Requirements Mapping to BRIDG<br />May 2010<br />20<br />Standards Influenced Research Information Systems Interoperability<br />
    21. 21. BRIDG Subset to CTRR DAM<br />May 2010<br />21<br />Standards Influenced Research Information Systems Interoperability<br />
    22. 22. CTRR DAM to CTRR HL7 Message RMIM<br />May 2010<br />22<br />Standards Influenced Research Information Systems Interoperability<br />
    23. 23. CTRR HL7 Message RMIM to HMD<br />May 2010<br />23<br />Standards Influenced Research Information Systems Interoperability<br />
    24. 24. CTRR HL7 MESSAGE HMD TO CTRR.XSD<br />May 2010<br />24<br />Standards Influenced Research Information Systems Interoperability<br />
    25. 25. From Requirements to HL7 Message<br />May 2010<br />25<br />Standards Influenced Research Information Systems Interoperability<br />
    26. 26. May 2010<br />26<br />Standards Influenced Research Information Systems Interoperability<br />
    27. 27. Semantic Interoperability Infrastructure<br />May 2010<br />27<br />Standards Influenced Research Information Systems Interoperability<br />
    28. 28. May 2010<br />28<br />Standards Influenced Research Information Systems Interoperability<br />
    29. 29. AbdulMalik Shakir<br />Information Management Strategist<br />City of Hope<br />1500 E. Duarte Road<br />Duarte, CA 91010<br />Office: (626) 256-4673 x63160<br /> Mobile: (626) 644-4491<br />Email: AShakir@COH.org<br />May 2010<br />29<br />Standards Influenced Research Information Systems Interoperability<br />

    ×