� ������ � ������� � ������ � ��������������� Authors: Wajahat Ali Khan, Maqbool Hussain, Muhammad Afzal, Khalid Latif, Hafiz Farooq , A.M Khattak Authors: Wajahat Ali Khan, Maqbool Hussain, Muhammad Afzal, Khalid Latif, Hafiz Farooq , A.M Khattak Presenter: Hafiz Farooq Ahmad National University of Sciences and Technology Islamabad, Pakistan �
� ������ � Introduction � Interaction Meta Model � Motivation � � � Workflow Artifacts Workflow Artifacts � Requirement and Approach Interaction Ontology � Proposed Extended Architecture � Relationship of Interaction Ontology with other Ontologies � � CITI Lab Example � Conclusion Future Work �
� ����������� � Pharmacy … … Patient Laboratory Administration Constitutes the set of The type of system Interactions describe the Initiate the transfer of rules for constructing the component that sends purpose of information information between message and receives the message flow system components Application Trigger Message Interactions Role Events Types
� � ��� ��������� � ����� � � ������������� Use Case Analysis of Laboratory Domain Example Test Order, Test Result etc Association of these use cases with HL7 messages Example Test Result Result Event Association of use cases with Interaction Model Example Process Artifacts for Test Order Message Development using information from different models Example MIF
� ���������� � ��� � ���� � sends Application Role Trigger Event 1 1 1 initiates receives receives 0..* 1 0..* Interaction 0..1 1..* 0..* responsible for transfers initiated by receiver 1 Message Type
� ��������� � � Perspectives of Semantic interoperability in � Perspectives of Semantic interoperability in HL7 V3 � Data (common terminologies) � Process (still a grey area)
� ������� � �������� Storyboards in HL7 Specifications Interactions, Storyboard contains Application Roles, interactions, Trigger Events � Process – values added activities interactions occurred between App. Roles. � Flow – time sequences, actors and cooperation RMIMs, DMIMs, RIM � Concept – definitions of and relations between concepts in process and flow models concepts in process and flow models � Information – classes and characteristics (attributes) for information regarding the concepts in the concept model To achieve semantic process interoperability we have to � standardize the processes, flows, concepts and information HL7 provides storyboards capturing limited scenarios, no � time sequences of interactions, no association of interaction with interaction sequences
� �������� ��� � ��� � ���� � Organization 1 Organization 2 Order Fulfillment Request Order Fulfillment Request (S:OP, R:OF) (S:OP, R:OF) Blockade Promise Activate Semantics (S:OF, R:OP) Order Confirm (S:OF, R:OP) Promise Confirm Response (S:OP, R:OF) Order Confirm Result Complete with (S:OF, R:OP) Fulfillment (S:OF, R:OP) Result Complete with Fulfillment (S:OF, R:OP)
� ���������� ��� � ������� � Requirement � Automate the process � � Semantics in Process Artifacts Semantics in Process Artifacts � Approach � Ontologies For interaction model constructs � � Rules Based on message contents �
� ���������� � �����!� �$ "� �������� �� � ������� #
� ���������� � �����!� �� "� ��������� # Trigger Event initiates interaction. Trigger Event initiates interaction. Interaction is the inverse of other Interaction is the inverse of other interaction. interaction . Application role plays role in Application role plays role in interaction. interaction. Interaction has receiver application Interaction has receiver application Interaction has receiver application Interaction has receiver application role. role. Interaction has Sender application Interaction has Sender application role. role. Message type is transferred by Message type is transferred by interaction. interaction.
� ���������� � �����!� �� "� ���������� � ��� # Application Role
� ���������� � �����!� �� "� ���������� # Interaction
� ���������� � �����!� �� "� ����!� � ��� # Message Type
� ���������� � �����!� �� "� ��!!�� � ���� # Trigger Event
� ���������� � �����!� �� "� ����������� # � Result Query Filler Order Confirm �
� ������� � %������ �� � ����������� ������������������� ������������������� ��������� ��������������� ��������������������������� ������������������ ����������������� ������������������ ������������������������ �������������������� �����
� ����������� �� � ���������� �� � �����!� ���� � ���� � �����!��� "��������#��������� ��""� ���������"� ���������� ! �������$������ ������ ! "��������#��������� "��������#��������� "��������#��������� �������$��%�������� �������$��%�������� ��""� ���������" �������$�� ��%���������������� ����������( ���������������$�� ����������������� ����������) ���������������� ****** ����������� "������ ����&"����''��� ������������ ��#��������������� ������ ! ������ ! �$���������� ����#�����
������ �� � %����� � � Scenario � Mrs. Bushra is examined by Dr. Jamil and reports extreme thirst, fatigue, and recent unexplained weight loss. unexplained weight loss. � She also reports having a family history of diabetes. � Dr. Jamil wants to rule out diabetes and wants to order the GTT tests.
�$ ������ �� � %����� " ���� # � Working � Two Systems: Ordering System and Laboratory System Steps � Test Order � � Ordering System to Laboratory System Message (m1) ⋀ hasMessageContent (m1, mc1) ⋀ TestOrder (mc1) Message Type (m1, mt1) ⋀ PlacerOrder (mt1) ⋀ InteractionID (m1, id1) ⋀ POLB_IN211100GB (id1) ⋀ SendingApplicationRole (m1,sar) ⋀ OrderPlacer (sar) ⋀ ReceivingApplicationRole (m1,rar) ⋀ OrderFulfiller (rar) ⋀ TriggerEvent (m1,te) ⋀ OrderFulfillmentRequest (te)
�� ������ �� � %����� " ���� # � Steps � Test Order Confirm Laboratory System to Ordering System � Message (m1) ⋀ hasMessageContent (m1, mc1) ⋀ TestOrderResult (mc1) Message Type (m1, mt1) ⋀ PlacerOrder (mt1) ⋀ InteractionID (m1, id1) ⋀ POLB_IN221000GB (id1) ⋀ SendingApplicationRole (m1,sar) ⋀ OrderFulfiller (sar) ⋀ ReceivingApplicationRole (m1,rar) ⋀ OrderPlacer (rar) ⋀ TriggerEvent (m1,te) ⋀ OrderConfirm (te)
�� ������ �� � %����� " ���� # � Steps Test Order Completion � � Laboratory System to Ordering System Message (m1) ⋀ hasMessageContent (m1, mc1) ⋀ TestOrderCompletion(mc1) Message (m1) ⋀ hasMessageContent (m1, mc1) ⋀ TestOrderCompletion(mc1) Message Type (m1, mt1) ⋀ ResultEvent(mt1) ⋀ InteractionID (m1, id1) ⋀ POLB_IN224200UV (id1) ⋀ SendingApplicationRole (m1,sar) ⋀ OrderFulfiller (sar) ⋀ ReceivingApplicationRole (m1,rar) ⋀ OrderPlacer (rar) ⋀ TriggerEvent (m1,te) ⋀ ResultCompleteWithFulfillment (te)
� ���������� � ������� �� �� ������ �� � %����� 1. Order Fulfillment Request 2. Order Confirm Order Placer AR Order Filler AR 3. Result Complete with Fulfillment
Recommend
More recommend