Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Low
-
Resolution: Fixed
-
Affects Version/s: TestManagement-3.5-RC3
-
Fix Version/s: Gazelle TM 5.4.5
-
Component/s: TF Concepts Management
-
Labels:None
-
Environment:Google Chrome
-
Severity:Blocker - Show stopper, feature completely blocked, crashes or data corruption
-
Sprint:Sprint 9, Sprint 10, Sprint 11, Sprint 12, Sprint 13, Sprint 16, Sprint 23, Sprint 24, Sprint 25, Sprint 26, Sprint 27, 2016 - S16, 2017 - S1
-
Account:NA-SUPPORT (NASUPPORT)
Description
I am defining a new option for a QRPH Supplement. I thought I would use the description from the supplement in the GMM description field and not just repeat the name of the option. When I include all of the text below, GMM throws an error. If I just use the first half, GMM accepts it.
Not a killer problem; low priority
This option defines the document submission requirements placed on form fillers for providing pre-pop data to the form Manager, describing specific content and vocabulary constraints to the PCC LDS that will optimize the ability to process the clinical content to fill in the BFDR Form. The Form Filler’s support for the VR Pre-Pop option determines how pre-population data is handled when the Form Filler retrieves the form using ITI-34:
If the Form Filler supports the VR Pre-Pop option, the value of the pre-popData parameter in the Retrieve Form Request (see RFD Trial Implementation Profile, section 2b:3.34.4.1.2) shall be a well-formed xml document as defined in the PCC Labor and Delivery Summary (LDS) Content Profile, and a well-formed xml document as defined in the PCC Labor and Delivery History and Physical (LDHP) Content Profile (see Labor and Delivery Profiles Trial Implementation Supplement, section Y.7) as constrained by QRPH 2: 6.3.1.A for the specification of the LDS content required.
Not a killer problem; low priority
This option defines the document submission requirements placed on form fillers for providing pre-pop data to the form Manager, describing specific content and vocabulary constraints to the PCC LDS that will optimize the ability to process the clinical content to fill in the BFDR Form. The Form Filler’s support for the VR Pre-Pop option determines how pre-population data is handled when the Form Filler retrieves the form using ITI-34:
If the Form Filler supports the VR Pre-Pop option, the value of the pre-popData parameter in the Retrieve Form Request (see RFD Trial Implementation Profile, section 2b:3.34.4.1.2) shall be a well-formed xml document as defined in the PCC Labor and Delivery Summary (LDS) Content Profile, and a well-formed xml document as defined in the PCC Labor and Delivery History and Physical (LDHP) Content Profile (see Labor and Delivery Profiles Trial Implementation Supplement, section Y.7) as constrained by QRPH 2: 6.3.1.A for the specification of the LDS content required.
