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

OO CR012-629 Placer and Filler ID Optionality Description

From HL7Wiki
Revision as of 19:05, 10 June 2010 by Hbuitendijk (talk | contribs) (New page: {{OO Open Change Requests}} {{OO Open V2.8 Change Requests}} Return to OO Change Requests page. {|width=100% cellspacing=0 cellpadding=2 border=1 || '''Su...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Return to OO Change Requests page.

Submitted by: Ruth Berge Revision date: <<Revision Date>>
Submitted date: 8-Jul-2009 Change request ID: OO CR012
Standard/IG: Standard Artifact ID, Name: <<Artifact ID, Name>>

Issue

See File:OO CR012-629.doc for problem definition and proposal.

Recommendation

Rationale

Discussion

  • 30-Jul-2009
  • We all realize the current condition rules for ORC2/3 & OBR2/3 are broken. The problem is constructing proper rules that handle the broad set of use cases where the ORC and OBR appear. There are messages where the ORC appears without the OBR (Rx for instance). There are 3 classes of messages, orders, events (results, administrations etc.) and queries. Any rules we devise need to take all these circumstances into account. We may end up with making the fields optional along with a lot of guidance on how to populate the fields in various circumstances.
  • 25-Sep-2009
    • Need to schedule further discussion time with Ruth and others on the call / in the room.
  • 15-Oct-2009
    • Further reviewed and suggested that Hans will take Ruth’s language, make some adjustments, and re-review.
  • 5-Nov-2009
    • Prep Notes
    • Best practice rules as we otherwise run into backwards compatibility issues.
    • Have general language of main purpose to have the ability to identify individual OBR/ORCs so they can be addressed later. Therefore you should not do the following (only list things you should not do). Note that a couple are SHALLs.
    • Placer
      • For Chapter 4 ORM, OML, Rx, etc., Med Rec Chapter, etc. (non-queries)
      • Either the Placer Number and/or the Filler Number must be present in either OBR or ORC, i.e.,
        • If only the ORC is present, either ORC-2 is valued, ORC-3 is valued, or both ORC-2 and ORC-3 are valued.
        • If only the OBR is present, either OBR-2 is valued, OBR-3 is valued, or both OBR-2 and OBR-3 are valued.
        • If both the ORC and OBR are present, then the following combinations are valid:
          • Only ORC-2 is valued
          • Only OBR-2 is valued
          • Only ORC-3 is valued
          • Only OBR-3 is valued
          • ORC-2 and ORC-3 are valued
          • OBR-2 and OBR-3 are valued
          • ORC-2 and OBR-2 are valued and are valued the same. SHALL
          • ORC-3 and OBR-3 are valued and are valued the same. SHALL
          • ORC-2, ORC-3, OBR-2, and OBR-3 are valued where ORC-2 and OBR-2 are valued the same and ORC-3 and OBR-3 are valued the same. SHALL
        • If both the ORC and OBR are present, then the following combinations are invalid:
          • ORC-2 and OBR-3 are valued
          • ORC-3 and OBR-2 are valued
          • ORC-2, ORC-3, and OBR-2 are valued
          • ORC-2, ORC-3, and OBR-3 are valued
          • ORC-2, OBR-2 and OBR-3 are valued
          • ORC-3, OBR-2 and OBR-3 are valued
          • ORC-2 and OBR-2 are valued where the values are different SHALL
          • ORC-3 and OBR-3 are valued where the values are different SHALL
      • If the message contains both ORC and OBR and ORC-2 and OBR-2 are valued, then they must be valued the same.
      • Chapter 7 results messages ORU, OUL, since no order needs to be present
        • If OBR-51 is valued, then neither ORC-2/OBR-2 nor ORC-3/OBR-3 need to be valued.
      • Queries
        • Query by example both may need to be blank in the query message.

• Response to query may just be results using OBR-51, therefore not requiring OBR-2/OBR-3/ORC-2/ORC-3 • If both the ORC and OBR are present in the query by example, then the following combinations are invalid: • ORC-2 and OBR-3 are valued • ORC-3 and OBR-2 are valued • ORC-2, ORC-3, and OBR-2 are valued • ORC-2, ORC-3, and OBR-3 are valued • ORC-2, OBR-2 and OBR-3 are valued • ORC-3, OBR-2 and OBR-3 are valued • ORC-2 and OBR-2 are valued where the values are different unless you want no response • ORC-3 and OBR-3 are valued where the values are different unless you want no response • If both the ORC and OBR are present in the response, then the following combinations are invalid: • ORC-2 and OBR-3 are valued • ORC-3 and OBR-2 are valued • ORC-2, ORC-3, and OBR-2 are valued • ORC-2, ORC-3, and OBR-3 are valued • ORC-2, OBR-2 and OBR-3 are valued • ORC-3, OBR-2 and OBR-3 are valued • ORC-2 and OBR-2 are valued where the values are different ORC-3 and OBR-3 are valued where the values are different • Filler o Refer to same conditional language as Placer. • Consider a table. • Post Meeting Note by Hans: We need to determine whether in that case ORC should not be present as there was no order, i.e., what would it mean to have an ORC without either a placer or filler order number? • December 3 o Rob Savage to take a stab at streamlined language to reflect this. Target Phoenix.

Recommended Action Items

Resolution

  • 12-Nov-2009
    • Austin: Move to accept proposal with proposed amendment – second by Rob Hausam, further discussion – no,
        • against:0, abstain: 0, in favor:11
Retrieved from "https://wiki.hl7.org/w/index.php?title=OO_CR012-629_Placer_and_Filler_ID_Optionality_Description&oldid=37752"