Uploaded image for project: 'PatientManager'
  1. PatientManager
  2. PAM-695

[PDQm Connector] GUI for PDQm R4 Consumer with query on _id

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 9.12.0
    • Component/s: PDQm/PDC
    • Labels:
      None
    • Business value:
      High - Major feature, it achieves a lot of work, influence depends on that
    • Frequency:
      Frequent - Regularly used feature or bug that happens often with common parameters
    • Sprint:
      2020 - S7
    • Account:
      Innovation 2020 (INNOVATION2020)
    • Epic Link:
    • Story Points:
      13
    • Original story points:
      13

      Description

      SUT operators must be able to send PDQm queries to their PDS SUT.

      Create a new page for PDQm R4.
      Reuse Template for SUT selection.
      Support only query on Id


      1. design, mockup (done) + sequence/class diagram
      2. Create XHTML GUI + managed Bean
      3. Integrate message browsing and patient view template.
      3. Create application layer (connect with existing GITB Client)

      Spec review, code review, TU on managed bean and app layer, Manuel test on gui (ATDD).



        BigPicture - Work Breakdown Structure

          Attachments

            Issue Links

            is cloned by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. PAM-723 [PIXm Connector] GUI for PIXm R4 Consumer with query on identifiers

            • Medium - Medium priority, must be plan in one of the next cycles.
            • Submitted

              Activity

                People

                Assignee:
                lchatty Luc Chatty
                Reporter:
                ceoche Cédric EOCHE-DUVAL
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - 2 weeks, 1 day, 3 hours
                    2w 1d 3h
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 1 week, 3 days, 7 hours, 30 minutes Time Not Required
                    1w 3d 7h 30m

                      Potential Duplicates