This wiki has undergone a migration to Confluence found Here

Lab Order Template

From HL7Wiki
Revision as of 19:59, 24 April 2012 by Ployd (talk | contribs)
Jump to navigation Jump to search

Back to Orders & Observations WG main page

Back to OO Projects page

Scope of Lab Order Template (ID: 587)

To develop a lab order model which meets the needs of lab for v3 and conforms to the composite order model as well.


Co-Chair, Project Facilitator, Modeling Facilitator: Patrick Loyd; 415-246-7441,

Modeling, SOA Facilitator: Lorraine Constable;


Link to the current document:

Conceptual Specification To Dos and Open Issues

  • September 2011 WGM
    • Create conceptual datatypes for items needed by conceptual models (done)
    • Review model interactions for consistency
    • Consider naming conventions for parts of the artifacts, and identifiers
    • Add the business context text to the use cases, and to the service specifications
  • January 2012 WGM
    • Review package structure and how to relate composite order model to lab models
    • Consider whether need a different package view for publishing purposes from working structure
    • Create Service-Specification Template of the spec documentation structure
    • Clean up state machines
      • Fulfillment or In progress
    • Create a communication diagram as an alternative to the sequence (determined not to do at this time)
    • Review of event flow
      • Clarify activity currently called "Patient Presents at Lab" to indicate that they are not actually presenting at the lab, maybe Patient Service Center, or just Patient Presents (done)
      • Expand lab activities to include steps like evaluating sample for suitability and notifying if rejected (done)
      • Expand diagram for the simple acute case where the collector goes to the patient (done)
      • Add a storyboard for the simple acute case where the collector goes to the patient (done)
      • Add a storyboard for the provider collects the specimen (done)
  • May 2012 WGM - Prep
    • separate interaction diagrams into two - one for each path in event flow - Lorraine
    • edit interaction to remove point of service - Lorraine
    • provide trace between analysis actors and the contract roles - Lorraine
    • plan call to create service scope verbiage - Lorraine
    • create second scenario for modify/cancel flow - Lorraine
    • document conformance statements in scenarios and contract interfaces - Lorraine
    • Create modify/delete event flow - Patrick
    • Fix swimlane problem in current create lab order event flow (lab repository is extra) - Patrick
    • Remove extra bits no longer used in the event flow - Patrick
  • Comments from Cindy V.:
    • Conceptual Roles: I suggest changing “healthcare information” in the description for the 2 systems to “laboratory information”.
      • PEL> Agree with change to Lab System actor. Will make the change
      • PEL> Do not agree with change to POS system. That actor is more general and available to everyone, not just lab. the intent of SAIF is to create re-usable bits. Overspecifying causes to lose this.
    • Conceptual State Model: I think it would be helpful to have a state model in the storyboards or before the comprehensive state model. This would fill in the gaps and help mess the see the derivation of “the following request object states and transitions from the above storyboards”.
      • Agree. Will add storyboard specific state machines for understandability as well as 'master' state machine
    • Conceptual State Model: The paragraph after the 1st state model starts “As you can see, the request object”. Frankly, I cannot see how the state model tracks from the storyboards. In addition, you use different terms in the state model such as fulfiller, fulfillment resolution, etc. that aren’t defined or, otherwise, explained.
      • Agree. Wording is left over from requirements document. Will reword accordingly.
    • In Contract Roles and Agents, you are using different terms for the Commissioning System Role and the Responsible System Role without linking them to the terms in the event flow (Provider Order Management System: Ordering System, Laboratory Point of Service System: Specimen Collector System, & Laboratory: Laboratory Information System). It would help in reading the more system-centric diagrams if this connection was made.
      • Agree. Will align.


  • Criterion mood to an attribute (preconditions)
  • Lab order is a proper subset of composite order (in two weeks)
    • composite order missing:
    • data enterer.modeCode
    • informationrecipient.sequenceNumber, info.rcpt.time
    • we are not using consistent sequenceNumber, should be there for all AR and Part where the min cardinality is 1 or higher
    • add subject to lab
    • lab order need location (yes)
    • should composite have reasonCode on placerGroup>?
    • update composite obs req and lab obs req for new negation ind
    • lab obs request, status must be mandatory
    • composite order, why ActDefinition.text (esp. as optional)
    • lab prioractrequest, remove code, text, correct spelling 'o'bsolete (lower case 'o')
    • does lab need preconidition

Completed RMIM To Dos

  • Review 'old' context conduction - DONE (PEL 20110911)
  • look at whether PatientorAssigned should still use R-assignedEntity - No change (PEL 20110911)
  • bring up to date to the current RIM - DONE (PEL 20110911)
  • Replace supporting clinical information CMET with supporting clinical statement
  • Replace annotation with annotation cmet
  • Add event to fulfillment AR
  • replace lab process step with process step cmet



IHE Laboratory-Clinical Communication Profile (LCC). Use cases and transaction patterns supporting laboratory order modification and results verification.