For Clinical Content Development Managers…
My key responsibilities with respect to clinical content in the EHR include:
1. Triaging submitted requests from clinicians and the order set build team
Issues may come to the team from clinicians at point-of-care, pharmacy labs, radiology, other departments, or even internally. It is important to organize, prioritize, and review the issues prior to assigning to the team.
Challenges:
I have broad reaching clinical issues that affect significant number of our order sets. How do I rapidly identify all the order sets affected? How does this affect other issues that are being worked on and the release schedule?
Solution:
Plexina provides reports where orders or order sets are used enabling quick assessment of where changes must occur. Plexina also identifies which resources are working on the content, and why, enabling the correct resource to address the broad issue simultaneously.
2. Organizing issues into releases
Challenges:
Order set changes have to fall into a release cycle. Given the other issues being addressed, when is the earliest possibility for this change to be addressed?
Solution:
Plexina captures level of effort associated with addressing issues. These effort values provide the metrics for estimation of effort, balancing work effort among the resources, and projecting out the expected timeline.
3. Assigning the changes to a resource
Challenges:
In a release you may have multiple changes that may affect the same order sets. How do I allocate the work to enable the efficient use of my team, and avoid conflicts?
Solution:
Plexina manages work assignments and provides reports which resource is addressing which issue, and what work is left. From this information you can assign the issue to the most suitable resource.
4. I need to account for how an error in the configuration made it into production
Challenges:
Configuration is limited to using the tools of the EHR which typically do not incorporate robust version control and issue management.
Configuration tools are typically limited to constructing the “what a screen should say” and do not concern themselves with the “how it got here”, and “what was the lifecycle of this order set”. As such, accidental changes in configuration, gaps in the release management and quality assurance process are virtually undetectable, require an investigation, or has an intensive paper-based process surrounding the entire order set management operation. With a manual paper-based process there are many opportunities for errors to be introduced.
Solution:
Plexina has integrated issue management, version control, release management, and workflow management with change detection, comparison reporting and release readiness reports. With a proactive change management process that is entirely optimized and electronically captured, unexpected changes show up explicitly to quality assurance teams. No change in the release is unintended and has a complete forensically reviewable history of its origin.