v0.5.0#20
Conversation
Unfortunately, this template does not have nice-looking stylings for buttons or forms. The CSS is rather complicated so it is not easy to adjust the underlying styling. For this, I've used inline styling to get forms to look decent. Inline styling was also done for the button.
I've restyled the dropdown box of health networks to appear closer to the design of the website. It's not strictly a material design, but is close enough. It would be nice to change the dropdown arrow, but that can be solved later.
* Changed name from 'signup' to 'apply' for consistency * Added introductory paragraph with explanation * Added maximum length to Illinois Physician License * Switched contact email to HealthyHomes
Draft of the Lead Safe application form
* Created an FAQ section in the menu * Created webpages for the English and Spanish FAQ * Added links to download PDF of the FAQ In the future, may rearrange this to "Resources for Parents" section as #16 progresses.
Include response codes to communicate the status of the API call through a specific field. The codes correspond to standard HTTP status codes.
Moved FAQ under a general "Clinical Content" section. Included a map of elevated BLLs in the section.
Iterated version to alpha3 and merged navigation elements to include clinical content and terms of service.
We added some work to dev and am rebasing. Iterated the proposed version number to v0.5.0-alpha4.
Added draft of response codes for #14
Changed error code labels to status code labels
|
@RaedMan - Please review the terms of service again for any issues. There is one obvious sentence that needs clarifying:
however, we will fix that when we release v0.6.0 of the API. |
|
I noticed a broken link in the notes of the main page, the https is missing the "h" should be |
|
Talked to @tomschenkjr and sounds like @RaedMan is working on the eligibility form, but for now the link is blank in the Eligibility section. Do we want to put in note that it's under construction or take the link out for now? Also I didn't see an open issue for this or a note in the wiki. This seems like a big task, I'm wondering if I missed it in the milestones. |
geneorama
left a comment
geneorama
left a comment
There was a problem hiding this comment.
I made a few minor changes and committed them to dev.
There was a problem hiding this comment.
Not sure where to add this in TOS:
"The use of the API precludes healthcare provider(s) and all staff, including third-party contractors, from the healthcare facility from transferring data or publishing any results derived from its activities hereunder and will not disclose any results or other material based upon data provided by the City without written permission from the City."
This may need some editing.
|
|
||
| Pediatricians are directed to test every Chicago child’s blood for lead and report high levels to the Chicago Department of Public Health (CDPH). According to the Centers for Disease Control and Prevention (CDC), the reference level of 5 micrograms/dL should be used to identify children with elevated blood lead levels and is based on U.S. children between the ages of 1 - 5 years old based on the 97.5th percentile of the National Health and Nutrition Examination Survey of blood lead distribution in children. | ||
|
|
||
| Though lead is no longer used in paint, plumbing, gasoline and a myriad of other products in the United States, Chicago’s older housing stock creates a persistent problem as homes built prior to 1978 that have not been properly maintained may still have older paint that can result in exposure to lead in children. This is especially true in some communities on the south and west sides of Chicago. |
There was a problem hiding this comment.
This is good information, but should it be part of the TOS?
There was a problem hiding this comment.
Since it was provided by CDPH, let's keep it unless they prefer to have different language.
|
|
||
| To ensure success in the fight against lead poisoning, this project is part of CDPH's overall plan to provide concrete steps that are being taken by the department and its partners to further reduce and eventually eliminate lead poisoning in Chicago’s children. | ||
|
|
||
| This lead safe predictive model helps identify infants at risk of being lead poisoned in homes with lead paint. The model provides an opportunity to prevent lead paint exposure through high priority proactive home lead inspections and blood testing at an earlier age. The predictive model combines data from multiple sectors including public health, census, buildings and the county assessor’s office to create real-time interfaces that identify where at-risk children live. |
There was a problem hiding this comment.
I'm not sure if we should have "background" in the terms of service, but wherever this content lands I propose that we use the terminology "infants and fetuses" here to make subsequent language easier. In the next paragraph we refer to "pregnant patients", which is confusing and perhaps technically incorrect.
There was a problem hiding this comment.
Likewise, to the above, we'll keep it unless CDPH wants something different.
|
|
||
| This lead safe predictive model helps identify infants at risk of being lead poisoned in homes with lead paint. The model provides an opportunity to prevent lead paint exposure through high priority proactive home lead inspections and blood testing at an earlier age. The predictive model combines data from multiple sectors including public health, census, buildings and the county assessor’s office to create real-time interfaces that identify where at-risk children live. | ||
|
|
||
| The risk score, defined as (XXXXXXXXXXX) will be sent to health centers through electronic health records (EHR) and physicians will have the opportunity to be alerted to either order a blood lead test and/or request to visually inspect the homes of either their pregnant patients and their at-risk children for lead paint hazards. |
There was a problem hiding this comment.
The risk score is part of the v0.6 milestone, but how do we want to describe the risk score here?
Also, I don't understand why we're saying that "physicians will have the opportunity to be alerted to either...". Will they be opting into the alerts?
In any event, I think the risk score documentation should be separate from the description of alerts, and I'm not sure that the risk score documentation belongs in the TOS.
There was a problem hiding this comment.
Yes, they will be provided information/alert/scores so the physician can order blood tests/visual inspections.
|
|
||
| Once You successfully integrate Your application with Chicago’s Test System, You may request an API key for the Production system. The City, in its sole and complete discretion, may give You an API key and access to the API. Upon submitting Your request You will receive an un-activated Production API Key. The City will review Your application to ensure compliance with the API Terms of Service. Once this has been verified, You will be notified that Your Production Key has been activated and is ready for use. | ||
|
|
||
| Access to the XXXXXX Environment is subject to Your compliance with these terms as well as development of a privacy policy, including clear and conspicuous disclosure to users of any practice whereby You or a third party collect or use personally identifiable information from users. In addition, You agree to fully comply with all applicable local, state and federal laws, rules and regulations relating to the collection of personally identifiable information, including personal health information and their associated privacy and security laws. Any violation of these requirements or failure to comply with Your privacy policy constitutes a violation of these TOS and is grounds for immediate termination of all access privileges to the API services and Data. |
There was a problem hiding this comment.
I'm not sure what the XXXXXX Environment means, so I'm not sure how to propose better terminology.
There was a problem hiding this comment.
Placeholder for the name of the application. Will be "Lead Safe". Will make it in the next release.
|
@RaedMan - I've included the language under the "City Policies and Requirements Regarding Use of API Services". Let me know your thoughts. |
|
@tomschenkjr thanks for the clarifications about what's going into .5 vs .6. This is good for .5. |
|
v0.5.0 has been deployed to the production servers! I am merging this code. I will be sending an email to health partners so they can conduct some testing. @RaedMan - the new web-based documentation will be updated as well. You can show the Lead Safe documentation to team members, which they can view in browsers: https://chicago.github.io/lead-safe-api-docs/ |
|
So far all the tests are passing (including expected errors), except for QA because there's a problem with the actual server. George has opened a ticket with EKI on that. |
3 participants
API
errorfield which provides any error messages from the request. (Added draft of response codes for #14 #17, Error conditions and expected results #14)Application Form
Clinical Content
After reviews have approved this request, I will only merge the request when we've pushed v0.5.0 into production.