Uploaded image for project: 'V2 Specification Feedback'
  1. V2 Specification Feedback
  2. V2-25489

Discrepancy between MSH-5 and MSH-6 cardinality

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • V2.x Message Specification (V2)
    • V2.9
    • Infrastructure & Messaging
    • Message Header (MSH)
    • Control (Chapter 2)
    • 2.13.9
    • Hide

      In V2.9 we changed the MSH-6 (Receiving Facility) RP/# value to Y (cardinality 0..*).

      We will initiate the appropriate HL7 process to revert this change. We will ask the CDSO (Dan) for assistance determining the appropriate process. 

      Will change MSH-6 to be non repeating in the next 2.9.1 ballot 

      Show
      In V2.9 we changed the MSH-6 (Receiving Facility) RP/# value to Y (cardinality 0..*). We will initiate the appropriate HL7 process to revert this change. We will ask the CDSO (Dan) for assistance determining the appropriate process.  Will change MSH-6 to be non repeating in the next 2.9.1 ballot 
    • Nick Radov / Michelle Barry : 2-0-0
    • Correction
    • Non-compatible
    • V2.9.1

    Description

      In V2.9 we changed the MSH-6 (Receiving Facility) RP/# value to Y (cardinality 0..*). That change was not present in the 2017 January ballot but was added in the 2017 September ballot. I couldn't find a record of that change, there are no votes about it in the 2017 January ballot results, and it isn't mentioned in the list of changes in 2017 September ballot. I suspect the change was introduced accidentally without following the proper process and thus it should be rolled back as a technical correction.
      This change has introduced a discrepancy with MSH-5 (Receiving Application) which does not have RP/# set to Y (cardinality 0..1). Even if it is potentially valid to send the same message to multiple facilities, those separate facilities won't share the same application.

      Attachments

        Activity

          People

            Unassigned Unassigned
            nradov Nick Radov
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: