| Other Best Practices | From C19HCC Digital Guideline WG: - Using CPG-on-FHIR standard for representing/ expressing the full intent of the Guidance in computer-interpretable artifacts (part of HL7 CPG-IG)
- Using the Agile Approach to CPG Development (inclusive of Integrated Process) to concurrently Produce Guidance and Make Guidance Computable (part of HL7 CPG-IG)
- Use Agile Knowledge Engineering methods, principles, and tools
- Cross-functional Integrated team (Agile CPG Team)
- Leverage composite nature of CPGs (e.g. can develop logic for inferences on patient information- CPG_CaseFeatures) to build incrementally and iteratively with rapid feedback
- Pull knowledge engineers into Content design/reviews; pull domain SMEs into knowledge representation design/reviews
- Leverage CPG-on-FHIR as a faithful expression of Guidance and its ability to create computationally derived CDS and Cognitive Support, patient-specific, practice-level digital Quality Measures/Metrics, eCaseReports, etc. to create computable artifacts used downstream in the Learning Health System and to provide closed-loop feedback/feedforward.
- Leverage established tools and capabilities (e.g. BPM+ process and tooling, Clinical Ontology) to author computable Guidance and Open Source tooling to translated into HL7 CPG-on-FHIR to leverage derivative and native compute
- tips:
- Use established standards and work with standards community (to understand and evolve as needed)
- Engage consumers/ users early and often
- Engage downstream vendors (e.g Terminology vendor USED in the EHRs) early
- Just because everyone everyone is using the same terminology systems doesn't mean they're agreeing how to use the actual terms- this needs to be considered and addressed to make ecosystem/supply chain work properly (feedforward from Evidence, but also feedback of data semantics back into evidence)
- Learn from related communities of practice (e.g. Agile Software Engineering)
|
|
|
|