¨ Team Tasks
§ Technical team members should begin assessment of the XML components for review and testing.
§ Content team members to review existing sections for the prototype and identify possible areas to standardize terminology (the semantics layer). Support the technical team where applicable.
¨ Overall Development Strategy
§ Approach will be based on an agile development methodology (i.e., short duration sprint deliverables)
¨ Out of Scope
§ The team will utilize only what is provided as the structure found in the existing PhUSE package. As such, any customization of the DRG is not in scope for this initial prototype release.
¨ In-Scope
§ Initiate an understanding and develop, test and inevitably represent an cSDRG in XML. This will be based on the prototype requirements listed below.
· Need working XML components (machine readable) and style sheet (human readable).
· Content & Technical members to conduct testing of package.
§ Prototype Recommendation:
· Title Page
· Table of Contents
· Section 1. Introductions
· Section 2. Protocol Description or Section 3. Subject Data Description
¨ Deliverable [Q2 2017]
§ Fully functioning prototype cSDRG in XML (template, example, style sheet, etc.)
§ Once agreement on a final package of such a prototype is achieved, this initial concept package will be considered the first deliverable for public consumption and feedback.
· 1-2 month public feedback period
¨ Feedback
§ It’s important to obtain preliminary feedback early on in the process to ensure our vision and approach is aligned with industry.
§ Identify best practices for final deliverable
Phase #2: Full cSDRG in XML Development [Q3-Q4 2017]
¨ Team Tasks
§ Review initial prototype public comments and make updates accordingly to prototype and remaining sections.
§ Technical team members should begin development of the remaining XML components for review and testing.
§ Content team members to review remaining sections terminology standardization (the semantics layer). Support the technical team where applicable.
¨ Scope
§ Develop and test remaining sections of the cSDRG in XML. This will be based on the prototype requirements listed below.
· Working XML components (machine readable) and style sheet (human readable) for entire cSDRG.
· Content & Technical members to conduct testing of final package.
· Cross-reference checking with define.xml
¨ Deliverable [Q3/Q4 2017]
§ Fully functioning cSDRG in XML (template, example, style sheet, etc.)
§ Once agreement on a final package of such a full cSDRG in XML is achieved, this will be considered the deliverable for public consumption and feedback.
· 1-2 month public feedback period
¨ Feedback
§ Review feedback from public and make update accordingly
Phase #3: Final cSDRG in XML Package Released [Q4 2017/Q1 2018]
¨ Team Tasks
§ Technical team members will make updates according to public feedback for final version release.
§ Content team members to support the technical team where applicable.
¨ Scope
§ Develop and test remaining sections of the cSDRG in XML. This will be based on the prototype requirements listed below.
· Working XML components (machine readable) and style sheet (human readable) for entire cSDRG.
· Content & Technical members to conduct testing of final package.
· Cross-reference checking with define.xml
¨ Deliverable [Q4 2017/Q1 2018]
§ Fully functioning cSDRG in XML (template, example, style sheet, etc.)
· Includes all updates pertaining to public comment period.
· Final release of the cSDRG in XML package to public
Phase #??: nSDRG and ADRG [TBD 2018]
¨ Additional details will follow regarding the development of nSDRG and ADRG once the cSDRG final package has neared completion for public release.
The deliverable schedule has been broken out into two agile phases, which have been provided below with estimated target dates. Please note, target dates may change dependent on team availability and complexity of those deliverable components.
Phase / Task Item / Est. Comp. Date / Actual Comp. Date / Comments1 / Phase #1: Proof of Concept (PoC) cSDRG Prototype / Q2 2017
1a / Review existing structure and tag XML and sematic elements / Q1 2017
1b / Develop draft material for team review / Q1 2017
1c / Initiate testing of final working material / Q1 2017
1d / Publish final package to wiki / Q1/Q2 2017
1e / Public Review / Q2 2017 / 1-2 Month Public Review Period
2 / Phase #2: Full cSDRG in XML Development / Q2-Q4 2017
2a / Review existing structure and tag XML and sematic elements / Q2/Q3 2017
2b / Develop draft material for team review / Q2/Q3 2017
2c / Initiate testing of final working material / Q2/Q3 2017
2d / Publish final package to wiki / Q3 2017
2e / Public Review / Q3/Q4 2017 / 1-2 Month Public Review Period
3 / Phase #3: Final cSDRG in XML Package Released / Q4 2017/Q1 2018
3a / Conduct final updates from public feedback / Q4 2017
3b / Initiate testing of final working material / Q4 2017/Q1 2018
3c / Publish final package to wiki / Q4 2017/Q1 2018
4 / Phase #??: nSDRG and ADRG / [TBD 2018]