Opened 8 years ago

Last modified 7 years ago

#130 new Enhancement

HP2020, HP2010, CSTE indicator pick list

Reported by: Lois Haggard Owned by:
Priority: +Medium Milestone: Needs Analysis
Component: Admin-App Version: Unknown
Severity: Major Effort Keywords: objectives
Cc: kneerings@…, Eleanor.Howell@…

Description (last modified by Garth Braithwaite)

Modify the current HP2010 application functionality and DB structure to include HP2020 alongside HP2010 objectives. Consider the addition of other indicator systems, such as CSTE Chronic Disease indicators, EPHT Nationally Consistent Data and Measures, others?

Garth/All?, would the steps be something like this?

  1. Make a ticket on the CoP Trac site (THIS TICKET) and assign it to the appropriate person/role (initially assigned to community member(s) to document user requirements).
  2. Start a forum thread in the IBIS Software Development and Documentation forum.
  3. Requirements development. An interested community member or members need to propose how it would work – from the user’s perspective. What would the Admin application screen(s) (e.g., pick list screens) look like? How would the app behave? What text would be included in the indicator report? What should happen if the indicator is in more than one indicator system (how to select it the citations, how to represent them in the indicator report)? How does this relate to the categorized index? This doesn’t need to be very detailed, but it needs to be enough to give the Java Developer a starting point.
  4. Community input. The User Requirements will be shared with the community via the forum. Community members will be asked to respond whether this functionality will be of benefit to the entire community (cost shared among all members) or only selected members (cost shared among selected members). Additional input from community members may fill conceptual gaps, raise questions and point out potential risks/drawbacks/issues.
  5. User requirements revised if needed.
  6. Analysis. The Java Developer/Garth? will need to consider how to achieve the user requirements. Do we need new DB tables? How many? Which ones? How will everything be hooked up?
  7. Prototype development. Java Developer begins working on it. He will work closely with the interested community member(s) to get his questions answered. A prototype/initial test version will be used to ensure that the requirements have been clearly communicated and correctly implemented. Additional questions will arise, and the developer and the interested community member(s) will address them as needed. Some questions may need to be directed toward the entire community.
  8. Community testing. Someone (either the Java Developer/Garth? or the interested community member(s)) will send out a notice to the community. Any interested community members may test the enhancement and offer suggestions.
  9. At some point, the interested community member(s) will “sign off” on the developed enhancement. It will then be included in the base code for adopters to adopt.

Ticket #141 is related/similar.

Attachments (2)

Issues with replacing HP2010 with HP2020 in Admin DB.docx (16.4 KB) - added by Garth Braithwaite 7 years ago.
HealthyPeople2020.xlsx (380.6 KB) - added by Garth Braithwaite 7 years ago.

Download all attachments as: .zip

Change History (17)

comment:1 Changed 8 years ago by Lois Haggard

Description: modified (diff)

comment:2 Changed 8 years ago by (none)

Milestone Parking Lot deleted

comment:3 Changed 8 years ago by Garth Braithwaite

Milestone: Unassigned
Owner: changed from Requirements Development to Unknown
Severity: Unknown
Version: 2.0Unknown

comment:4 Changed 8 years ago by Garth Braithwaite

Severity: UnknownMajor

Kim Neerings asked me to spend some time to look into HPO solutions. So this only applies to how the HPO could be handled.

Here's my understanding:

1) multiple HPO indexes. For now we'd have 2010 and 2020 but this mechanism can allow to have as many as we'd need. 2) HPO should be assigned to the view NOT the indicator. 3) A view can be applied to multiple HPO indexes - different index sets or within the same index.

If this is the case then my solution is to create a master HPO INDEX table that would have a NAME, TITLE, DESCRIPTION, SORT_ORDER. I'd then change the focus area table to something like HPO SECTION and tie to the hpo index table. HPO would then continue to tie to the focus area (SECTION). We'd then have an intersection table between the IV and the HPO. The view XSLT code would be changed to list the view's HPOs by the HPO index. The HPO would be dropped from the IP pages.

To do this requires DB structure changes (including removing the HPO from the IP), DB data changes, new JSPs (index definition page, IPV to HPO, changes to existing HPO pages to handle changes, major changes to the indicator HPO page), new Java data structure and controller code that handles the new struct and all the new insert and deletes that would be needed. The publishing code would also need some work. The view's XSLT code for HPO would need some updates. Finally, all the IPs would need to be republished.

None of this is a huge deal so my initial estimate is approx 2 weeks but as things have been going it would probably end up 4 taking weeks by the time it's all said and done.

comment:5 Changed 8 years ago by Garth Braithwaite

Added initial take on a general HEALTH_OBJECTIVE table structure see 3171.

comment:6 Changed 7 years ago by Garth Braithwaite

Description: modified (diff)

comment:7 Changed 7 years ago by Kim Neerings

Cc: kneerings@… added

comment:8 Changed 7 years ago by Kim Neerings

UT, NC, NJ definitely interested; NM (and others) would benefit.

comment:9 Changed 7 years ago by Kim Neerings

Milestone: Unassigned2.2 - Feature Set Definition
Version: Unknown2.2

comment:10 Changed 7 years ago by Eleanor Howell

Cc: Eleanor.Howell@… added

comment:11 Changed 7 years ago by Garth Braithwaite

Milestone: 2.2 - Feature Set DefinitionNeeds Analysis
Version: 2.2Unknown

comment:12 Changed 7 years ago by Eleanor Howell

Keywords: indicator categories added

comment:13 Changed 7 years ago by Eleanor Howell

Keywords: objectives added; indicator categories removed

Changed 7 years ago by Garth Braithwaite

Changed 7 years ago by Garth Braithwaite

Attachment: HealthyPeople2020.xlsx added

comment:14 Changed 7 years ago by Garth Braithwaite

Text from email tread: Kim asked me to spend some time to look into HPO solutions as she needs to do trainings next week. Who all do we need to involve in defining what exactly is wanted.

Here's my understanding:

1) multiple HPO indexes. For now we'd have 2010 and 2020 but this mechanism can allow to have as many as we'd need. 2) HPO should be assigned to the view NOT the indicator. 3) A view can be applied to multiple HPO indexes - different index sets or within the same index.

If this is the case then my solution is to create an HPO index table that would have a NAME, TITLE, DESCRIPTION, SORT_ORDER. I'd then change the focus area table to something like HPO SECTION and tie to the index. HPO would then continue to tie to the focus area (SECTION). We'd then have an intersection table between the IV and the HPO. The view code would be changed to list the view's HPOs by the HPO index.

To do this requires DB structure changes (including removing the HPO from the IP), DB data changes, new JSPs (index definition page, IPV to HPO, changes to existing HPO pages to handle changes, major changes to the indicator HPO page), new Java data structure and controller code that handles the new struct and all the new insert and deletes that would be needed. The publishing code would also need some work. The view's XSLT code for HPO would need some updates. Finally, all the IPs would need to be republished.

None of this is a huge deal so my initial estimate is approx 2 weeks but as things have been going would probably end up 4 taking weeks by the time it's all said and done.

I'll add this info to the ticket and will let you the CoP discuss the priority etc. Please let me know if the 3 specs listed above are correct.

comment:15 Changed 7 years ago by ken

1) multiple HPO indexes

I would strongly agree with this if it could be used to accommodate other "standard" sets of health indicators (such as the CSTE Chronic Disease Indicators).

2) HPO should be assigned to the view NOT the indicator.

I would strongly agree with this. Otherwise, you're locked into having every view in a given IP correpond to the same objective with the same operational definition (as we are now), which is not always very helpful. (For example, one might want to look at seat belt usage as a health indicator using both observational estimates and self-report, which are distinctly different measures.)

Note: See TracTickets for help on using tickets.