I’m incredibly grateful for this opportunity and excited to contribute to OpenMRS and make a meaningful impact. Looking forward to learning, building, and collaborating with this amazing community.
Hello team, I am currently working on immunization workspace refactoring. In the immunization workspace, I need to add an extra field called ‘notes’ (comments). However, the FHIR resource in OpenMRS is not updated for this field, and I cannot map the notes.
Greetings @chintu, after looking a bit, you were right with your comment on last week’s O3 squad call: There were some immunization options available in CIEL that we didn’t have. This PR will update the list to add 19 more options. Let me know if in your feedback you hear of other vaccines that are missing - these were all the missing ones I personally could find in CIEL.
Ready for Next Release (with testing): As a general view-only overview of the patients’ history, it’s great. I’d like to get this into the very next O3 Release. @chintu@dennis could you put this behind a feature flag for now at least, or even pop it into dev3 directly without a feature flag? (@chintu please just test it a bunch see if you can force it to do anything weird! )
Expires Date (Most Important point of feedback): While I’d say this is fine as the “MVP”, what’s really missing to elevate this to a level that will really help providers is showing the " Date coverage expires / Valid until" date. (And then making it red if that date is in the past.) What needs to happen in order for us to show this information? Are we waiting on some kind of backend variable? Do you just need a concept for “Valid until” to support the Entry/Edit form itself?
Dennis mentioned a while ago that in the Immunizations FHIR resource, you couldn’t find a “valid until” field. Do you just need either (a) for me an Ian to suggest an alternative FHIR resource, or (b) for us to invent something in the OpenMRS data model? Or a concept for it?
Yes, there is an expiration date which is already being recorded in the form, but it falls under vaccination batch information, so it’s not about the patient’s immunization coverage timeline - it’s literally just about the expiry date of the vial/injection itself used to inject/insert into the patient. So yeah, not the same
App order: Please move the history view up so it’s above the entry/edit widget. Why: It’s easier to skim than the edit/entry widget, and the other open source EMR that guided our design for this follows a similar pattern.
Horizontal Scroll Bar: As soon as there is data that goes past the user’s horizontal screen display, can we please show the Horizontal Scroll Bar by default (so not on hover)? This is to make it easier for the vast majority of our users who do not have a trackpad that easily responds to left/right horizontal scroll hand movements. (Most users are on a very old desktop with an old or simple mouse, or on a tablet.)
Immunization App Text: Please update the text so instead of “Single Dose on [date]”, it says “Last dose [date], Dose # [dose number]”, as shown in the image below. This is more clear for users
The “More than 10” Bug: Dennis mentioned a while ago that in the immunization widget, when adding vaccinations or doses, if more than 10 entries are added, the form accepts them but doesn’t display entries beyond the 10th. Did you already fix this? If not, please fix
FHIR represents “next vaccination” as a separate resource (ImmunizationRecommendation) that we don’t currently support. Realistically the concept of “date of next dose due” is not usually part of the vaccination record. It’s probably beyond the scope of the GSoC project to add the data model and API to support that.
However, since the core part of the project is building an Immunization History Card, we would ideally need a “vaccination valid until” field to help flag patients appropriately.
I came across the FHIR Immunization extensions and was wondering — would it be a valid approach to use or define a custom extension on the Immunization resource to store this information?
Please let me know if this could be a feasible path forward, or if there’s a better alternative you’d suggest.
Hi @ibacher,
Just following up on the discussion around the “valid until” / “coverage expiry” field for immunizations.
I understand we’re not currently supporting ImmunizationRecommendation, so I was wondering if you’d had a chance to consider whether we could proceed with a custom extension on the Immunization resource, or if you’d prefer we explore another approach
I’ve been thinking about the approach for implementing nextDoseDate. It would be cleaner and more consistent if we tied it to a concept, similar to how other immunization data points are handled.
Project Title: Immunization and Vaccination Schedule in O3
Primary Mentor: [@dkigen]
Backup Mentor: [@grace]
Project Goals
Resources:
see if you can force it to do anything weird! )