Lab UV SB Simple Request
Back to OO Behavioral Model Conceptual Specification (Draft)
Universal Storyboard - Create Lab Order
To start, the simplest use case:
Eve Everywoman, a 27-year-old female, presents at Good Health Hospital Outpatient Clinic and is seen by Dr. Patricia Primary. Eve reports a history of Anemia and recent, excessive tiredness. Dr. Primary enters a request to check the iron levels in Eve’s blood into her care system. Dr. Primary’s care system then sends the test requests to the lab system at the Good Health Hospital’s Laboratory service. Eve receives a paper order requisition that serves as a reminder, provides instructions for where to find the collection center, and also details preparation instructions for the patient to follow (no food or drink from midnight until collection time on the day of collection). Later that week Eve presents herself at the Lab Collection Center. The lab looks up and finds the order for her testing in the lab system. The appropriate blood samples are extracted, their containers labeled, and the sample information added to the information in the lab system. The lab performs the analysis on the specimen(s), adds the results to the lab system, and sends the results to Dr. Primary’s care system reported as final. Dr. Primary reviews the results, formulates a treatment, if needed, and notifies Eve Everywoman of the results and treatment.
At its most basic, the business process documented in this use case is one of a requested service and documentation when that service is performed. Many ambulatory use cases follow this basic pattern and the only communications are the two, the first from placer to filler with the request and the second from the filler to the placer with the fulfillment of that request.
The following figure shows the flow of the storyboard using an Activity Diagram. File:Create Laboratory Order Activity Diagram.png
Back to Lab Order Conceptual Specification (Draft)