Uploaded image for project: 'HPDSimulator'
  1. HPDSimulator
  2. HPD-146

Issues reported by eHealthSuisse HPD users

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.3
    • Component/s: None
    • Labels:
      None
    • Account:
      eHealthSuisse - GL01 (EHEALTHSUIGL01)

      Description

      Hi,

      I have found validation differences between the IHE EVS validation and the EPR Central Service Interface Specification.
      1. assertionId=IHEHPD-071: The "hcRegistrationStatus" attribute (objectClass HCProfessional) is required.
          According to the Central Service Interface Documentation (chapter 4.2.3.2), this attribute is not supported.
      2. assertionId=CH-HPD-010: The "memberOf" attribute is required.
          According to the Central Service Interface Documentation (chapter 4.2.4.2), this attribute is read-only and can not be defined in the feed request.
          In case of the query, the provider attribute "memberOf" is derived from the "member" attribute of the relationship the provider belongs to.
      3. assertionId=IHEHPD-037: The "hcSpecialisation" attribute shall be formatted as follows: "Issuing Authority:Code System:Code:CodeDisplayName".
          According to the Central Service Interface Documentation (chapter 45.3.4), all coded attributes (incl. the specialization) shall be formatted as following:
          "Issuing Authority:Code System:Code" (without "CodeDisplayName").
         
      That means requests that successfully create providers in the central service will not be accepted by the EVS Client.
      How can we solve that?

        Attachments

        There are no Sub-Tasks for this issue.

          Activity

            People

            • Assignee:
              aberge Anne-Gaelle Berge
              Reporter:
              epoiseau Eric Poiseau
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 3 hours, 45 minutes Original Estimate - 3 hours, 45 minutes
                3h 45m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 5 hours, 15 minutes
                5h 15m

                  Potential Duplicates