Uploaded image for project: 'Gazelle HL7 Validator'
  1. Gazelle HL7 Validator
  2. HLVAL-304

Inconsistent validation for HL7-DE

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: Gazelle HL7 Validator 3.2.0
    • Fix Version/s: None
    • Component/s: HL7v2 Validator (core)
    • Labels:
      None
    • Sprint:
      2016 - S4, 2016 - S5, 2016 - S7
    • Account:
      Maintenance 2016 (MAINTENANCE2016)

      Description

      a user of our IHE-D-profiles working with https://gazelle.ihe.net/EVSClient/hl7v2/validator.seam?extension=IHE%20Germany reported the following issue.

       

      Taking the attached ADT message and validating it against the profile 2.16.840.1.113883.2.6.9.47 (https://gazelle.ihe.net/GazelleHL7Validator//viewProfile.seam?oid=2.16.840.1.113883.2.6.9.47),

      two errors are returned:
      Type Data type error
      Location ADT_A03/PV1[0]/PV1-36(Discharge Disposition)[0]
      Value 092
      Description Datatype DLD does not match the one declared in the message profile (IS)

      Type Data type error
      Location ADT_A03/PV1[0]/PV1-45(Discharge Date/Time)[0]
      Value 20160226130325
      Description Datatype NM does not match the one declared in the message profile (TS)
      However, the message seems to have valid and plausible values at PV1-36 (IS) and PV1-45 (TS).

      The error description refers to datatypes DLD and NM, which occur in PV1-37, PV1-46, like there is some sort of "one off" behavior involved...

        BigPicture - Work Breakdown Structure

          Attachments

            Activity

              People

              Assignee:
              aberge Anne-Gaelle Berge
              Reporter:
              aberge Anne-Gaelle Berge
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                BigPicture - Skills

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - 30 minutes
                    30m
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 30 minutes
                    30m

                      Potential Duplicates