NOTES: Action items can be found on slide 27 Agenda Items for Feb 23 meeting are on the next page. Key changes in the document: P. 2: agenda for next meeting Pp . 17-19: discussion with Lloyd on what is a DAM and the techniques to use
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Action items can be found on slide 27
Agenda Items for Feb 23 meeting are on the next page
Key changes in the document:
P. 2: agenda for next meeting
Pp. 17-19: discussion with Lloyd on what is a DAM and the techniques to use
Pp. 38-68: description of the HDF DAP approach for a DAM, including artefacts
André Boudreau (firstname.lastname@example.org)
Laura Heermann Langford (Laura.Heermann@imail.org)
2011-02-16 (No. 2)
2011-02-09 (No. 1)
HL7 Patient Care Work group
Source: HDF 1.5 R1 (Nov. 2009), Section 3- Domain Analysis Process (DAP): Analysis and Requirements Documentation
Source: HDF_1.5.doc, page 37
The purpose of the following diagram is to describe the process used to identify the actors and use cases in a formalized structure that enables Domain Experts and Business Requirements Analysts to identify the functional interoperability scenarios.
Document Actors' Actions: Analyze the storyboards to identify the systems, business actors, and functions/actions performed.
Describe interoperability use cases: Describe the conditions under which information is exchanged and the responsibilities of each actor based on information received.
Refine the steps in the use case model: Clarify and expand the storyboard into an Activity Diagram. The Activity Diagram will visualize the activities and flow of a healthcare business process. The facilitator will use UML to document these process steps.
Document Information Exchange: The process flow is broken into steps and then the message exchange is clearly illustrated. Special care will be paid to message processing rules and to identifying the business triggers.
Review may require several iterations
The information model and its associated diagrams document the static syntactic and semantic relationships of importance in the healthcare business process including the responsible parties/entities and the various data elements/structures required by the process. The semantic meaning of each item and attribute in the information model is described in the model documentation. The following diagram describes the steps required to develop the information analysis artifacts.
See next page
Analyze state transitions for business objects: Analyze the data exchange requirements that appear as Data Objects in the Activity Diagrams. Document the life cycle of each of these data objects in UML State Diagrams.
Analyze other business rules: Analyze the Story Boards and Activity Diagrams to determine Business Rules and conditions that are not adequately captured in the Domain Analysis Model, Domain Glossary and State Chart. A complete DAM will include a thorough analysis of business rules governing the processing and exchanging information in order to meet interoperability requirements.