Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

 BA's or Feature Leader's checklist

4 Must-Do’s

  • 1. Problem Description: Have you clearly defined the user problem(s) you intend to solve, and what value this creates? Write down a story, user insight, or quote about this problem (this is important because (1) this will motivate your team, and (2) without this your problem might not actually be a big problem for the users themselves).
  • 2. User Stories: Have you clearly written at least 3 user stories and use cases? 
  • 3. Market Analysis: Have you surveyed what the market is doing here (e.g. comparison to other EMRs, or paper approaches; and don’t forget about learning from historic/existing OMRS instances)? Have you written down any possible gaps in your understanding of your users or their workflows? Have you reviewed the topic in FHIR to see what requirements or fields the global community references? (Eg if working on insurance, should look here)
  • 4. Technical Considerations & Dependencies: Have you outlined what you need from cross-functional areas for success of the feature? E.g. do you need the platform to support a new API call? Have you explained how you’ve addressed dev concerns, such as designs that may not be feasible, or will be extra time-intensive to implement? 

Optional/Encouraged

  • Sketches: Have you added a drawing or description of how the feature could work to solve the problem at hand? (Pictures of sketches are ok!) 
  • Project Management: Have you created the Epic and JIRA tasks so you can share work clearly? Roll-out plan: Do you have an idea whether this will be an experiment, gradual roll out, and when? Have you added this to the timeline view? Have you planned how you will promote and/or work with communications folks in order to help this feature reach the widest audience and have the biggest impact it can?

Later but should do

  • QA Plan: Have you mentioned the plan for QA, such as how you will discover and address edge cases? Does your team/squad have a plan for automated tests to be added to new components (unit tests) or workflows (e2e tests)?
  • Safety & Tech Risks: Is there any reason you could regret rolling out this feature? (e.g. possible patient harm, heavy tech debt like introducing an unsupported library) Have you thought through the risks for this particular solution? And, how to reduce/address those? 

This checklist was inspired by this article. Additional Business Analyst Resources here.

Summary:

  • OpenMRS needs a solution for:

    • (1) a CDS Engine,

    • (2) Authoring that's Clinician-friendly,

    • (3) a way to test rules, and;

    • (4) sources of content that are trustworthy, free, and actively maintained.

Contents:

image-20250220-143419.png

1. Problem

A Recipe for CDS

CDS is a massive topical field. It helps to think about it as a “Recipe” with some key “Ingredients” (components). We need a solution for each of these.

A Recipe for CDS

Ingredient

Notes

How we plan to solve this

🧠 Brain / CDS Engine

Examples include:

  • CQL Engine/cql-framework

Drools

Authoring that’s Clinician- and BA-Friendly

BA-friendly way to represent and write rules, content

Way to safely QA / review rules that is Clinician- or BA-friendly.

DMN (graph/chart), BPMN (), decision tables

Way to test rules

This is usually overlooked.

Content

Examples include:

  • RxNorm

  • SNOMED CT

  • UpToDate

GAP. Need to find: Are there public datasets out there?

2. User Stories

3. Market Analysis

Helpful links & resources from previous CDS initiatives:

SMART Guidelines & CQL “101”

https://www.youtube.com/watch?v=w_wuUoFAp7I&ab_channel=OpenMRS

Explaining our approach to SMART Guidelines & CQL Engine in 2023.

image-20250220-141704.png
image-20250220-141629.pngimage-20250220-141651.png

4. Technical Considerations & Dependencies

5. QA Plan:

TBC: The plan for QA, such as how we will discover and address edge cases

TBC: Plan for automated tests to be added to new components (unit tests) or workflows (e2e tests)

6. Safety & Tech Risks

TBC: Is there any reason you could regret rolling out this feature? (e.g. possible patient harm, heavy tech debt like introducing an unsupported library)

TBC: Have you thought through the risks for this particular solution? And, how to reduce/address those? 

  • No labels