TrueHealth HIV CDS Y2 Lessons Learned
- Andrea Price (Deactivated)
Source:
Instructions
We would like to provide you some guidance for how to effectively use the following template
How should use this document?Â
- This document should be used for you to register any milestones, good or bad, throughout our project that may be used to help future participants
- We do not have any expectation about what the milestones should be, so you should document them as much as you can.
- We are hoping that by reviewing this document anyone will be able to see how your process for implementing our project went
The cells that are grayed-out serves as an example of what you could document
Here is a brief description of the data points listed:
| Data Point | Description |
|---|---|
Date | Should be the date of the event/milestone you are describing-- use the first of the month if the specific date isn't known |
| Challenge or Best Practice | Select Challenge if this you identified a roadblock regardless of whether you were able to resolve it. If it is an observation, innovation or opportunity, select Best Practice. |
| Category | Suggested categories include Data (extracting, entry, validation, etc.), Implementation (integrating into the EHR or HIT system), Roll out (training, challenges at the site with administration, payment, staffing, etc.), Workflow (difficulty in integrating into practice, innovation in care pathway, etc.), Experience (patient or care team feedback--positive or negative, innovations to improve experience, patient-centered changes, care team-centered changes, etc.). You can propose or add additional categories if needed but be judicious. |
| Description | Describe the issue in as much detail as you can. It could describe a challenge you encountered, an innovation you developed, a finding that surprised you (A-ha! Moment), or a practical modification or solution that made you more efficient or effective. |
| What went well | Use this space to provide a brief description of what do you think worked out well. Even if you are reporting a challenge, try to provide the positive aspects of the situation or you may leave this blank. Perhaps things went as expected or maybe another department provided the support needed for staff to buy into the project |
| What is blocking you or did not go well | The opposite of the above-- even if it's an innovation there may be barriers to implementing it. Specifically mention any blockers and include those which are external and may not be able to be overcome in the foreseeable future. If there was nothing negative, you can leave this blank |
How did you address or would you correct this for next time? | This field will differ slightly based on the issue type. What did you do to address the challenge? How did you implement your solution or innovation? What will you do differently next time? If you will test the solution and consider new changes in the future, you can say that. |
| Follow Up | Is the milestone fully accomplished or there are next steps? If so, briefly describe them |
| Solution Team | Who is or are the point person(s) to provide more detail or participated in the development of the innovation/solution |
Lessons Learned: Challenges and Best PracticesÂ
OCHIN
| Date | Challenge or Best Practice | Category | Description                (Use your own words) | What went well and why? | What is blocking you or did not go well and why? | How did you address or would you correct this for next time? | Is there any follow up needed? | Solution Team |
|---|---|---|---|---|---|---|---|---|
| 2023-03 | Challenge | Implementation | Delayed implementation of HIV CDS tool at participating CHC. | The tool was designed and built in a timely manner. No issues with OCHIN resourcing. | Competing organizational priorities. This includes clinical quality priorities as well as general institutional priorities. This is causing a barrier in CHC engagement and ability to meet more regularly. | Current focus is to provide CHC project champion with many choices to meet and be diligent with follow up to secure a meeting time. In the future, we would set a meeting cadence from the start and adjust where more or fewer meetings are needed to successfully complete implementation in a timely fashion. | There is currently no follow up needed as we were able to schedule with the CHC and are planning to implement shortly after that meeting. | Project Manager |
| 2023-03 | Best Practice | Data | Having a data dictionary and a clear data ask made this task straightforward for our lead Data Analyst. | The data dictionary is a great resource that helps tailor the extract to the correct specifications. | There was an initial misunderstanding about having the dataset be for a select service area and not the entire OCHIN collaborative. | Our Data Analyst reran the numbers for the specific service area we are partnered with and sent the specific dataset. | No follow up needed at this time. | Data Analyst |
| 2023-03 | Challenge | Data | Thin dataset | We still have 7 full months of data shared with NACHC (Oct 2022-Apr 2023) | Howard Brown Health is a new member that went live with OCHIN Epic in Sept 2022. The data available shifts significantly from <20 encounters to >8K in Sep 2022. | There is nothing we can do about the missing data from months prior to their OCHIN go-live because we do not have this data in Epic to export. In the future, we will make note of this when submitting the datasets and consider this when recruiting partners. | No follow up needed at this time. | Data Analyst and Project Manager |
Select One:
| Issue | + | - | ? | Who can speak about this issue? | Who can speak about this issue? | ||
Select One:
| ||||||||
Dear Confluence Users, If you need support for use of Atlassian tools, please contact informatics@nachc.com whether you have technical issues, need feature assistance, or simply have questions.