Source:
| Tip |
|---|
...
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:
...
Date
...
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
...
How did you address or would you correct this for next time?
...
Lessons Learned: Challenges and Best Practices
...
...
| title | 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 |
|---|---|---|---|---|---|---|---|---|
YYYY-MM-DD | Select One:
| Select One:
| Issue | + | - | ? | Next Steps | Who can speak about this issue? |
Example 2020-04-20 | Challenge | Data | Missing patients on our data pull | We were able to get the majority of patients on first data pull | Many patients who received vaccines were missing on our initial pull | Team did some reviews of patient charts and discovered that encounter code 992XX was missing from the data pull. Next time we should have a medical provider review the list of encounters. We standardized the data pull so it can be reused. | Create standard queries for encounters and common conditions so they become standardized. Look for unusual encounter codes to make sure coding is appropriate. Obtain feedback from chief medical officer about list of requirements and where data points are located within the EHR | HIT data manager |
3/23/2022 | ||||||||
| Tip |
|---|