Question

Please read the following scenario and then create the deliverable listed below, 1) Use case diagram 2) Interaction diagram 3) Create the core and supporting classes of the RIM (Entity, Role, Role Relationship, Participation, Act, Act Relationship) similar to the one in slide 20 in the live session Note: Copy the MS VISIO diagrams and paste them onto a word document and then submit only one word file to the assignment submission link. Scenario Mrs. Annie Nuclear showed symptoms such as sudden onset of fever, headache, and stiff neck for the past 3 days. Annie Nuclear suddenly fell down and lost consciousness and 911 was called. Your solution will be addressing the following section. The message models (design part) will be for the whole scenario. The HL7 v2.x or v3 message implementation can be limited to one interaction mentioned in this scenario. After admitting into the ER, she was treated with mild antibiotics and samples of blood and cerebrospinal fluid were sent for testing. Annie Nuclear was then moved to an isolation ward at the Greenville hospital. Dr. Admit, the clinician for Annie Nuclear, has not yet received the laboratory results, but based on clinical findings (ER) he believes this to be a suspect case of Meningococcal Meningitis (MM)[1]. The doctor sends an investigation request to the local public health unit indicating that lab tests have been ordered but no results are available yet. Nightingale working at the local public health unit accepts the investigation request. She creates a “suspect” case for Annie and then follows up by sending the hospital a care plan request message. This message recommends that the hospital place Annie on respiratory isolation until 24 hours after the commencement of treatment. Nightingale goes to the hospital to see Annie and initiates contact tracing. Annie identifies sixteen people (all within her extended family) with whom she’s recently shared meals. Nightingale records these individuals as close contacts of this case. In the meantime Nightingale receives confirmation of MM from the Laboratory through Laboratory Result Notification. The Lab has sent these results to Public Health because this is a notifiable condition. Dr. Admit treats Annie Nuclear for MM and immediately administers antibiotics; since the MM was diagnosed at a very early stage, Annie Nuclear made a thorough recovery.

Answer 1

Use Case Diagrams.:

1. Use case diagrams are usually referred to as behavior diagrams used to describe a set of actions (use cases) that some system or systems (subject) should or can perform in collaboration with one or more external users of the system (actors). Use cases are a set of actions, services, and functions that the system needs to perform.

• Actor. Actors are usually individuals involved with the system defined according to their roles. ...
• Use Case. A use case describes how actors use a system to accomplish a particular goal. ...
• Relationship. The relationships between and among the actors and the use cases.
• System Boundary.

2. Interaction diagrams are models that describe how a group of objects collaborate in some behavior - typically a single use-case. The diagrams show a number of example objects and the messages that are passed between these objects within the use-case.

3.

Action – the focus of health care communication and documentation The reason we want to automate health care data is to be able to document the actions taken to treat a patient: A request or order for a test is an action. The report of the test result is an action.Creating a diagnosis based on test results is an action.Prescribing treatment based on the diagnosis is an action In simple terms, a medical record is a record of each of the individual actions that make up the diagnosis, treatment, and care of a patient.

レmet- ク

Acts Have Moods…

Further clarifies the meaning of the Act (like Class and Code)

• Specifies if this act is an actual fact (event), or an intention to perform an act - such as a command, goal, appointment, or proposal.
• Signifies a major modality or stage for which a permanent record must be obtained.
• Never changes.
• Alternatively, status can change.
• Status does not define the Act.

Types of Act Relationships :

• COMP - has component
• PERT - has pertinent info
• SEQL - is sequel
• OPTN - has option
• FLFS - fulfills
• RSON - has reason
• INST - instantiates
• PRCN - has precondition
• OUTC - has outcome
• ARR – arrived by
• SUCC - succeeds
• RPLC - replaces
• OCCR - occurrence
• REFV - has reference values
• AUTH - authorized by
• COST - has cost
• GOAL - has goal
• PREV - has previous instance