Feature: EIR / Vaccination Card

[lache-melvin]

Vaccination Card

Spec document

Breakdown

Create and Maintain Immunisation Programs

• [x] #4652
• [x] #4653
• [ ] #4654
• [ ] #4655
• [ ] #4656
• [ ] #4657

Vaccination Card

• [x] #4660
• [x] #4661
• [ ] #4663
  • [ ] #4665
  • [x] #4737
  • [ ] Delivered dose modal links to related encounter
  • [ ] Add a progress bar summarising the immunisation schedule
• [ ] Capture adherence against each immunisation schedule
• [ ] Capture patient withdrawal - program withdrawn -> adherence shows this?
• [x] #4675
  • [ ] Add customisable encounter types (“Fixe”, Avancée” & “Mobile” )
  • [ ] Highlight the period of the patient's age
  • [ ] Highlight doses the patient is ready to receive in this encounter (in the period(s) that a patient is currently within, if min interval has passed)
  • [ ] Hide past periods, unless a vaccination was missed in that period
  • [ ] Highlight the period of the patient's age
  • [x] #4710
  • [x] #4711
  • [ ] Batch not required if encounter date is in the past
  • [ ] Or if not given, capture reason (refused/out of stock)
  • [ ] #4713

Encounters changes

• [x] #4712
• [x] #4709
• [ ] #4714
• [ ] Delete vaccinations
• [ ] Delete vaccinations when encounter is deleted
• [ ] When finalising, create next scheduled encounter
• [ ] Add free text clinician to encounter
• [ ] Default encounter date to today
• [ ] When pulling a patient from central, also pull encounter data
  • [ ] Sync encounter data between sites (if a patient is at multiple)
• [ ] Link to the created prescription from an encounter
• [ ] Capture/show facility on encounter
• [ ] Can create an encounter from another facility

Patient Management improvements (if time)

• [ ] New patient creation in one single form
• [ ] Add Enrolment in program to creation form
• [ ] When there is only one program, it should be default selected during enrolment
• [ ] Improve the patient search flow when creating patients
• [ ] Remove patients from a facility (transfer to another facility/they move overseas)
• [ ] Delete a patient (if no transactions)

Moneyworks Jobcode 🧰

[DJIGVCDV]

Testing

Setup

• [ ] Clone programschemas repo (for now you'll need to check out the immunisation-programs branch) and from the repo root, run ./build_all_immunisation_program.sh
• [ ] Configure an immunisation program in mSupply
  • Create a master list for the program (Items > Master Lists) (it will need at least one item)
  • Under Program Settings
    • Check This master list is a program
    • Check Immunisation program
    • Create a Program tag
  • Then under Special > Stores > your store > Master Lists, make the new master list visible
  • Add JSON schemas to document registry (Toolbar Special tab > Show document registry...)
    • Create new document for program enrolment
    • e.g. Document type: SomeImmunisationProgramEnrolment, category: PROGRAM_ENROLMENT, context: your_new_master_list, name: Some Immunisation Program
    • Data schema: from programschemas repo - generated/immunisation_program/immunisation_program.json
    • UI schema: from programschemas repo - immunisation_program/ui_schemas/immunisation_program_ui_schema.json
    • Create new document for encounter
    • e.g. Document type: SomeImmunisationProgramEncounter, category: ENCOUNTER, context: your_new_master_list, name: Some Immunisation Program Encounter
    • Data schema: from programschemas repo - generated/immunisation_program/encounter_creation.json
    • UI schema: from programschemas repo - immunisation_program/ui_schemas/immunisation_program_encounter_ui_schema.json
  • Under Admin > Edit Users > Your user > Open mSupply Permissions, add view and edit permissions for your program (ensure you are setting perms for the correct store 😁)
• [ ] Add the Open mSupply: Uses program module store preference, and ensure store is a dispensary

Testing steps

• [ ] As a central user, you can create an Immunisation Program

[adamdewey]

Yo @lache-melvin - I'm getting a bit confused - an immunization schedule IS an immunizaton program so I'm getting a bit confused by the distinction made here.

Why do we need a specific preference to enable immunization schedules and to link schedules to programs?

[lache-melvin]

@adamdewey hehe this is definitely a draft, and I'm still learning my way around a lot of this language, so please forgive 😁

There is some level of distinction in that we created "immunisation programs" for GAPS, but they don't currently link in with patient programs. So in the absence of better naming, the plan is to:

• Change immunisation programs in OMS central (the stuff from GAPS) to be immunisation schedule configuration
• Configure a base patient program for each immunisation program (so we sync through legacy mSupply, and get all the existing patient program functionality)
• In OMS, link that program to the immunisation schedule configuration - then when patients enrol in this program, we can create the vaccine card based on the immunisation schedule configuration

...does that make sense?

[adamdewey]

Thanks @lache-melvin !

So I think first thing to clarify is that mine and @richardmoizeau's vision behind the Programs section in Open mSupply wasn't to be just for immunizations, it was to serve as a focal point for top-level users to manage all things program-related at the top level.

I.e. it would ultimately serve as the go-to place for top-level users who wanted to configure global system settings for HIV, TB, immunization programs etc (also thinking forward to when OG is dropped).

For the rest:

Change immunisation programs in OMS central (the stuff from GAPS) to be immunisation schedule configuration

I'm not sure I understand this - does this mean re-naming everything to remove the word 'Program'? I don't think we should do that..

Configure a base patient program for each immunisation program (so we sync through legacy mSupply, and get all the existing patient program functionality)

Can this be done on the back-end without exposing to the user that there are 'two kinds' of program?

In OMS, link that program to the immunisation schedule configuration - then when patients enrol in this program, we can create the vaccine card based on the immunisation schedule configuration

I think we should link in the backend but not make the distinction to the user - it would be better for them to think that programs and schedules are the same thing in the UI.

Ideally they would just put the word 'Schedule' into the name of their immunization program

[lache-melvin]

Caught up in person.. to summarise:

• Immunisation programs need to be patient programs, so they need to be first configured through mSupply
• Then in omSupply, the Programs > Immunizations screen is where we would mark these programs as Immunization Programs, and add the additional configuration (the vaccine courses etc.)

So not renaming, just moving from omSupply creating immunisation programs, to it configuring a previously created patient program to be an Immunisation Program.

I'll update wording everywhere to be Immunisation Program, I think that's easier?