This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "OO Behavioral Model"

From HL7Wiki
Jump to navigation Jump to search
 
(33 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
<[[Orders & Observations TC]]>
+
{| style="width:100%; background-color:transparent;"
 +
|-
 +
| style="vertical-align:top" | <!-- LEFT COLUMN -->
 +
== Project Objectives & Introduction ==
 +
The [[OOBF_CC_20100922 | SAIF Behavioral Model]] project has superceded the OO Dynamic Model project.  Below are the old definitions and materials, which are not updated at this point.
  
−
== Project Objectives ==
+
 
 +
The objective of the OO [[Dynamic Model]] project is to initially focus on common set of rules on how to deal with order management state transitions after the creation of an order.  This will cover Lab, Rx, Rad, PT, Dietary, NRS, Procedures, etc.
 +
<p>
 +
Subsequently we will focus on:
 +
<ul>
 +
<li>Create set of rules on how to deal with observation state transitions</li>
 +
<li>Synchronize with [[Referral]]s and appointments.</li>
 +
<ul>
 +
 
 +
| style="vertical-align:top" | <!-- RIGHT COLUMN -->
 +
 
 +
<div style="float:right;">
 +
<div style="background:#ffffff; padding:0.4em; font-size: 95%;">
 +
{{OO Wiki Contents}}
 +
</div>
 +
</div>
 +
|}
 +
 
 +
=== Approach ===
 +
<ul>
 +
<li>This wiki page will be used to focus our discussions.</li>
 +
<li>We agreed to use the Publishing Database directly to maintain the necessary ballot components ([[Storyboard]]s, [[Interaction]]s, [[Trigger Event]]s, [[Application Role]]s, [[State Transition]]s) and Visio for the [[Activity Diagram]]s. The Activity Diagrams form the core of the new [[Communication Process Model]] concept which has yet to be formally approved.</li>
 +
<li>Creating ballotable artifacts will be the main driver, while the decisions and notes from the minutes will be input into the documentation</li>
 +
<li>For the state machine we will start with the currently defined general state machine and then specialize the definitions and descriptions for Orders & Observations.
 +
</ul>
 +
Michael van Campen and Garry Cruickshank will drive populating the Publishing Database based on our input, while Wendell Ocasio will put the initial Activity Diagrams into Visio based on our input.
  
 
== Story Boards ==
 
== Story Boards ==
 +
===Story Board One===
 +
* Doctor orders for an inpatient coumadin, 2mg, QD, start=now, end=open.
 +
* Doctor reviews the lab results and determines that she needs to change the coumadin order, increasing the dosage to 3mg QD starting today (before the next scheduled administration).
 +
* The patient has a procedure tomorrow requiring suspension of the medication effective 00:00.
 +
* The patient returns from the procedure and the physician indicates resumption with the next scheduled dose.
 +
 +
===Story Board Two===
 +
* Patient is in ICU and doctor orders TPN with the following additives [CalciumGluconate, PotassiumChloride, MultiVitamin, SodiumChloride], at a rate of 50CC/HR.
 +
* During morning rounds, around 07:00, the doctor orders an MRI to be taken around 10:00 and suspends the TPN effective 09:00 through 13:00.
 +
* While the pharmacist reviews the patient record around 10:00, he recommends to change the TPN and increase the SodiumChloride.
 +
* The pharmacist enters the changes and the doctor verifies the revision.
 +
* The next day the doctor orders a the rate to be reduced to 25CC/HR.
 +
* Three days later the doctor discontinues the TPN.
 +
 +
=== Story Board Three===
 +
* Doctor orders gentamicin sulfate 80mg IM, Q8H at 06:00, 14:00, 22:00.
 +
* Patients goes for a test at 13:00 and returns 17:00.
 +
* The 14:00 dose is now administered at 17:00 and the schedule is shifted to 17:00, 01:00, 09:00.
 +
* Two days later the order is discontinued.
 +
 +
  
 
== Activity Diagrams ==
 
== Activity Diagrams ==
  
 
== Interactions ==
 
== Interactions ==
 +
<ul>
 +
<li>Composite Order Cancel(POOR_IN200903UV)</li>
 +
<li>Composite Order Complete(POOR_IN200908UV)</li>
 +
<li>Composite Order Fulfillment Request(POOR_IN200901UV)</li>
 +
<li>Composite Order Nullify(POOR_IN200906UV)</li>
 +
<li>Composite Order Replace(POOR_IN200907UV)</li>
 +
<li>Composite Order Resume(POOR_IN200905UV)</li>
 +
<li>Composite Order Revision(POOR_IN200902UV)</li>
 +
<li>Composite Order Suspend(POOR_IN200904UV)</li>
 +
<li>Placer Composite Order Number Assigned Response(POOR_IN200911UV)</li>
 +
<li>Send Placer Composite Order Number(POOR_IN200910UV)</li>
 +
</ul>
 +
 +
== Interaction Diagram ==
 +
[[Image:POOR.jpg]]
  
 
== Trigger Events ==
 
== Trigger Events ==
Line 16: Line 81:
  
 
== Dynamic Model Minutes ==
 
== Dynamic Model Minutes ==
−
To get access to just the Dynamic Model related minutes from past O&O meetings, please click [[OO Dynamic Model Minutes|here]].
+
To get access to just the Dynamic Model related minutes from past O&O meetings, please click [[image:Dynamic Model minutes.doc]]
 +
 
 +
'''[[OO Dynamic Model Minutes|here]]'''.
  
−
<[[Orders & Observations TC]]>
+
<[[Orders & Observations WG]]>

Latest revision as of 19:56, 23 September 2010

Project Objectives & Introduction

The SAIF Behavioral Model project has superceded the OO Dynamic Model project. Below are the old definitions and materials, which are not updated at this point.


The objective of the OO Dynamic Model project is to initially focus on common set of rules on how to deal with order management state transitions after the creation of an order. This will cover Lab, Rx, Rad, PT, Dietary, NRS, Procedures, etc.

Subsequently we will focus on:

  • Create set of rules on how to deal with observation state transitions
  • Synchronize with Referrals and appointments.

Approach

  • This wiki page will be used to focus our discussions.
  • We agreed to use the Publishing Database directly to maintain the necessary ballot components (Storyboards, Interactions, Trigger Events, Application Roles, State Transitions) and Visio for the Activity Diagrams. The Activity Diagrams form the core of the new Communication Process Model concept which has yet to be formally approved.
  • Creating ballotable artifacts will be the main driver, while the decisions and notes from the minutes will be input into the documentation
  • For the state machine we will start with the currently defined general state machine and then specialize the definitions and descriptions for Orders & Observations.

Michael van Campen and Garry Cruickshank will drive populating the Publishing Database based on our input, while Wendell Ocasio will put the initial Activity Diagrams into Visio based on our input.

Story Boards

Story Board One

  • Doctor orders for an inpatient coumadin, 2mg, QD, start=now, end=open.
  • Doctor reviews the lab results and determines that she needs to change the coumadin order, increasing the dosage to 3mg QD starting today (before the next scheduled administration).
  • The patient has a procedure tomorrow requiring suspension of the medication effective 00:00.
  • The patient returns from the procedure and the physician indicates resumption with the next scheduled dose.

Story Board Two

  • Patient is in ICU and doctor orders TPN with the following additives [CalciumGluconate, PotassiumChloride, MultiVitamin, SodiumChloride], at a rate of 50CC/HR.
  • During morning rounds, around 07:00, the doctor orders an MRI to be taken around 10:00 and suspends the TPN effective 09:00 through 13:00.
  • While the pharmacist reviews the patient record around 10:00, he recommends to change the TPN and increase the SodiumChloride.
  • The pharmacist enters the changes and the doctor verifies the revision.
  • The next day the doctor orders a the rate to be reduced to 25CC/HR.
  • Three days later the doctor discontinues the TPN.

Story Board Three

  • Doctor orders gentamicin sulfate 80mg IM, Q8H at 06:00, 14:00, 22:00.
  • Patients goes for a test at 13:00 and returns 17:00.
  • The 14:00 dose is now administered at 17:00 and the schedule is shifted to 17:00, 01:00, 09:00.
  • Two days later the order is discontinued.


Activity Diagrams

Interactions

  • Composite Order Cancel(POOR_IN200903UV)
  • Composite Order Complete(POOR_IN200908UV)
  • Composite Order Fulfillment Request(POOR_IN200901UV)
  • Composite Order Nullify(POOR_IN200906UV)
  • Composite Order Replace(POOR_IN200907UV)
  • Composite Order Resume(POOR_IN200905UV)
  • Composite Order Revision(POOR_IN200902UV)
  • Composite Order Suspend(POOR_IN200904UV)
  • Placer Composite Order Number Assigned Response(POOR_IN200911UV)
  • Send Placer Composite Order Number(POOR_IN200910UV)

Interaction Diagram

POOR.jpg

Trigger Events

Application Roles

State Transition Definitions

Dynamic Model Minutes

To get access to just the Dynamic Model related minutes from past O&O meetings, please click File:Dynamic Model minutes.doc

here.

<Orders & Observations WG>

Retrieved from "https://wiki.hl7.org/w/index.php?title=OO_Behavioral_Model&oldid=41151"