Closed tomschenkjr closed 6 years ago
Create Eligibility Intake Form (draft):
1. Name of Health Network (see list below for drop-down menu options and consider other FQHCs found on the portal)
2. Clinical Point of Contact a. Name b. Title c. National Provider Identifier d. Illinois Physician License (Should we include nurses, NPs, etc) e. Contact Information: Address, Telephone, Email
3. Technical Point of Contact a. Name b. Title c. Contact Information: Address, Telephone, Email
4. Eligibility Criteria I have read the Eligibility Criteria and certify that this institution meets the minimum standards.
5. Terms of Service I have read the Terms of Service I accept the Terms and Service I do not accept the Terms of Service
Hospitals within Chicago for drop down:
Policy for approvals and next steps in discussion, but approvals may need to occur as pilots one-one-at-a-time.
Thanks, Raed. This looks like a good first draft. We may want a sentence or two of who the clinical point of contact should be and who the technical point of contact should be. DoIT can draft the latter if CDPH can draft the former.
@wesleycoates - you mentioned the list on the portal may be out-of-date. Is there an updated list? I've also looked on data.gov, but don't think I see a federal dataset, unfortunately.
Nicely done Raed. Yes Tom, that list is certainly out of date (2014), but somewhat actionable. Raed, Sheri Cohen curated that list based on something similar from HRSA.. I am not familiar enough with the criteria to know what qualifies, but we can check around and see if we can get that updated.
Re: 2. Clinical Point of Contact (draft) The clinical point of contact should be a physician licensed to practice medicine in all its branches as defined by the Illinois Medical Practice Act of 1987.
The physician shall be an authority or in a senior management position at their healthcare facility or program (the healthcare facility and program as defined by the Illinois Department of Public Health). The physician is expected to be a champion for the lead safe project, as well as willing to provide support or commit resources on behalf of the healthcare facility and program. This physician is generally in charge of medical matters and often is the superior of other physicians, but may also be in charge of other professional groups and areas of responsibility. In many healthcare facilities and programs, this person may have the title of the most senior physician, (e.g., chief physician, head physician, physician in chief, chief of medicine, chief medical officer, chief resident, chief of staff, etc.,) or they may also have the title of the most senior physician of a particular department (e.g., department chair) but they don't necessarily require any the titles noted in the above examples.
@RaedMan - for NPI and IPL, is there a minimum length for the identifier? Is it just numeric or are there letters, too?
I can add some validation to the form to make sure length requirements are being met.
I've mocked-up an initial draft of the form based on @RaedMan initial draft. Attached is a screenshot (click for a larger image) of the code that is currently sitting on issue2
branch. Let me know if there are any changes that are needed, if not, I think we can share this with others.
Before this can be finalized, will need the correct email address to use.
@tomschenkjr Great work! As for your questions:
Update: email address HealthyHomes@cityofchicago.org is approved.
I've updated the form and created a pull request #15 that documents the changes so far. Please take a look as I've uploaded the screenshots of the application and how an application will appear in email.
This is a pretty complete draft, but not entirely done with this issue. When we're ready to deploy, still need the following changes:
select input
)Also, I should note that HealthyHomes@cityofchicago.org will be sent all the email (in the To: line) while developers@cityofchicago.org (which DOIT can access) will be CC'd.
@wesleycoates can the ARF be amended for HealthyHomes@cityofchicago.org to include developers@cityofchicago.org or @tomschenkjr is this something you all can do?
Everything looks great - thanks @tomschenkjr
No need for an ARF. DOIT already has access to that email (we use it, for example, as notifications for registering with the Open311 API). You’ll still control the process, we just get a heads-up so we’re also aware and can plan accordingly.
From: Raed Mansour [mailto:notifications@github.com] Sent: Thursday, October 19, 2017 5:20 PM To: Chicago/lead-safe-api-docs lead-safe-api-docs@noreply.github.com Cc: Schenk, Tom Tom.Schenk@cityofchicago.org; Mention mention@noreply.github.com Subject: Re: [Chicago/lead-safe-api-docs] Eligibility criteria & process for new institutions (#2)
@wesleycoateshttps://github.com/wesleycoates can the ARF be amended to include developers@cityofchicago.orgmailto:developers@cityofchicago.org or @tomschenkjrhttps://github.com/tomschenkjr is this something you all can do?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/Chicago/lead-safe-api-docs/issues/2#issuecomment-338054110, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkC0TcTUH9Vid3QNq3aeN_HY5mSlXmDks5st8sSgaJpZM4O_W2e.
This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail (or the person responsible for delivering this document to the intended recipient), you are hereby notified that any dissemination, distribution, printing or copying of this e-mail, and any attachment thereto, is strictly prohibited. If you have received this e-mail in error, please respond to the individual sending the message, and permanently delete the original and any copy of any e-mail and printout thereof.
I bet Christine has acted on the ARF already -- meaning Unisys is already creating healthyhomes@cityofchicago.org
Check with her tomorrow and see -- if not, she just needs to create another through another ARF
On Thu, Oct 19, 2017 at 5:20 PM, Raed Mansour notifications@github.com wrote:
@wesleycoates https://github.com/wesleycoates can the ARF be amended to include developers@cityofchicago.org or @tomschenkjr https://github.com/tomschenkjr is this something you all can do?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Chicago/lead-safe-api-docs/issues/2#issuecomment-338054110, or mute the thread https://github.com/notifications/unsubscribe-auth/AGRgRA9RN7cNfwYQ54U42moozoW_LW-lks5st8sSgaJpZM4O_W2e .
@wesleycoates Sorry, I didn't mean to imply we need to create developers@cityofchicago.org, just that when a message is sent to healthyhomes@cityofchicago.org, besides me, that it also gets sent to the developers email. I thought the ARF was needed.
The main remaining item left for this issue is eligibility requirements. The current draft of the form points to eligibility requirements separately from terms of service. Are these the same or separate? If separate, what are the eligibility requirements?
@RaedMan - I've moved this particular issue to be finished in v0.6.0 of the API (the next release). We will need the eligibility requirements so we can list them on the webpage.
Would it be possible to get the eligibility requirements before January 19th?
@tomschenkjr Yes, and the eligibility requirement for the clinical side is an amalgam of the form above plus the piece about the draft Clinical Point of Contact paragraph from above. I can fuse it into written form (ie, must have a license, must be a hospital listed below, etc) and can definitely have it done this week.
A missing component is a Technical piece and what is needed to make it happen. Perhaps referencing the repos needed may suffice, but this may vary across health systems. Borrowing from the RWJF grant were as follows if this works:
Scope of Work EHR trigger to notify at-risk patients/families against a geographic database of Chicago lead risk. EHR trigger is based on age and pregnancy status patient list of patient at-risk to be notified in at the patient office visit and in real-time with a trigger notification alert. CDPH maintains a geographical listing of at-risk properties.
Deliverables CDPH will provide access to an updated database where queries are made to the server based on child patient age and/or a mother’s prenatal visits and patient address. Queries handled to include, triggers, XML file, and Clinical Decision Support. At risk notification to provider or care coordinators to communicate to the patient.
Git Hub Link Codes Model ETL API
Anticipated Resources Professional Services, Project Management, IT Development, Licenses, etc. All costs for development, programming and support should be planned for and are borne by the healthcare facility and not by the City of Chicago.
Not sure about that last section on resources.
Eligibility Criteria
In order to access the Lead Safe API, you must comply with the following criteria:
1. Must be a Healthcare Facility or Program as Defined by the Illinois Department of Public Health in the City of Chicago. See the list of qualified facilities in Chicago.
2. Healthcare Facility Must Have a Clinical Point of Contact The clinical point of contact should be a physician licensed to practice medicine in all its branches as defined by the Illinois Medical Practice Act of 1987. The physician shall be an authority or in a senior management position at their healthcare facility or program (the healthcare facility and program as defined by the Illinois Department of Public Health. The physician is expected to be a champion for the lead safe project, as well as willing to provide support or commit resources on behalf of the healthcare facility and program. This physician is generally in charge of medical matters and often is the superior of other physicians, but may also be in charge of other professional groups and areas of responsibility. In many healthcare facilities and programs, this person may have the title of the most senior physician, (e.g., chief physician, head physician, physician in chief, chief of medicine, chief medical officer, chief resident, chief of staff, etc.,) or they may also have the title of the most senior physician of a particular department (e.g., department chair) but they don't necessarily require any the titles noted in the above examples.
3. Healthcare Facility Must Have a Technical Point of Contact The technical point of contact should be someone authorized to make changes to their Electronic Health Record (EHR) either through internal facility staff or external contractors and have a working understanding of HIPAA privacy and security rules, Health Information Technology (HIT) Standards and Application Programming Interfaces in HIT. The following describes the technical scope of work and expectations involved, but is not necessarily limited to these:
Scope of Work EHR trigger to notify at-risk patients/families against a geographic database of Chicago lead risk. EHR trigger is based on age and pregnancy status patient list of patient at-risk to be notified in at the patient office visit and in real-time with a trigger notification alert. CDPH maintains a geographical listing of at-risk properties.
Deliverables The Chicago Department of Public Health will provide access to an updated database where queries are made to the server based on child patient age and/or a mother’s prenatal visits and patient address. Queries handled to include, triggers, XML file, and Clinical Decision Support. At risk notification to provider or care coordinators to communicate to the patient.
Git Hub Link Codes
Anticipated Resources Professional Services, Project Management, IT Development, Licenses, etc. Note that all costs for development, programming and support should be planned for and will be borne by the healthcare facility and not by the City of Chicago.
4. Privacy Official Under HIPAA (Health Insurance Portability and Accountability Act of 1996) the healthcare facility's privacy official (the privacy official may have other titles and duties in addition to his/her privacy official designation in a typical healthcare facility setting) shall oversee all Lead Safe API development, implementation, maintenance and compliance to the healthcare facility's privacy policies in accordance with applicable federal, state, and local laws. HIPAA for purposes of this document includes HIPAA, HITECH and Omnibus requirements.
@tomschenkjr @geneorama @wesleycoates Regarding eligibility, this draft can go up after "3. Healthcare Facility Must Have a Technical Point of Contact" component is reviewed because I wasn't sure how in depth it should go. Also, if this goes up, should we add "DRAFT" somewhere until it goes through the process of approvals?
Right now, there is stock language on the eligibility of health systems and a faux-link to a sign-up form. In reality, we need to determine what institutions are eligible, the actual sign-up process, and any supporting materials that the institutions are required to submit.