Closed Candice-Louw closed 1 year ago
Thanks for the lot of work.
I asked the relevant colleagues of our health departement about the vaccinations. They told me, that for us it makes only sense to fill in the vaccination if we have a contact or case. According to what we know we are only allowed to save the vaccinations of that persons, but not for all vaccinated persons if they are not a case, contact or event participant. This persons would have to proof the vaccination by the vaccination pass or similar. For that reason it would be good if there could be a check-box like
[_] Vaccination proofed / Impfung nachgewiesen
or a pull-down-menu with
Vaccination proofed / Impfung nachgewiesen Vaccination not proofed / Impfung nicht nachgewiesen Vaccination will be proofed / Impfung wird nachgewiesen/Wurde zum Nachweis der Impfung aufgefordert
This might be special for Thuringia where the vaccinations are organized by the Association of Health Insurance Doctors in behalf of the state. Other states are organizing it by themself and having maybe lists of all vaccinated persons.
@Marko-ilmkreis - thank you for the feedback! [20.01.2021] This will be refined to be incorporated into the design.
WISH | DE: Further wish from GA Fürth, Günzburg, Kelheim (Schulung and ticket system) - a map that shows in which village, district etc. there are already vaccinated cases and contacts.
Comment: this would only be possible at a later stage after the basic functionality of the module has been defined and is operational. Could also be possible through the use of https://github.com/hzi-braunschweig/SORMAS-Stats once complete.
WISH | DE: Dear Sormas team, For the case processing in Sormas we need data fields for vaccination. The following fields are required:
@Candice-Louw We already have vaccination documentation in the system for vaccine preventable diseases like measles (https://release-international.sormas.netzlink.com/sormas-ui/)
We just need to refine it and activate for covid. This is how it looks
As @Marko-ilmkreis mentioned, if the goal is to document the vaccination status of the case, contact, ep, then we just need to add all the remaining variables and activate this for COVID. We did not include it initially because covid had no vaccine then.
Since the immunization module presented in the other issue is more generic, I would suggest that we to not link them for now. When the immunization module would be ready, then we can then map data from immunization to the vaccination part of the case.
@Candice-Louw can we migrate this to a new issue? not to get confused with the main immunization ticket
@Johannes-Schmidt-GA-RT : Please feel free to add any additional comments/input/feedback.
@Candice-Louw We don't need it in great detail. @bernardsilenou suggestion would be almost enough for us, the only thing missing is the vaccine that was vaccinated. This is all the information SurvNet needs. The Immunizations details should be shown in the Person entity.
@Johannes-Schmidt-GA-RT - great, thank you for the feedback!
@tobiasschellhorn @carolinverset @ftavin : Please feel free to add any additional comments/input/feedback.
I have added a summary for changes to be made for vaccination status here #4137. We can then maintain this ticket for immunization module.
GK 23-Jan-21 00:17:
„Comirnaty“ is the commercial name of the vaccine produced by the company BioNtec; its international nonpropriotory name (INN) is „tozinameran“
Every medical product usually has a commercial name and a INN. Different companies can produce the same INN either under a different or under the same commercial name. Also the same Product can be marketed by the same company under different commercial names in different countries. And of course one and the same company can potentially produce more than one type of vaccine against COVID, so that the only truly identifying name is the INN, which is why it was invented. Unfortunately the INN is not alway used.
So for identifying a vaccine it would be best to offer four fields À) commercial name B) INN C) Company producing it D) batch number „Chargen Nummer“
Won't be introduced for Person-only entities [Person-only entities won't be introduced in SORMAS per the Review 23.02.2021 feedback]. Replaced by https://github.com/hzi-braunschweig/SORMAS-Project/issues/4137
Reopened per discussion 02.03.2021
@MateStrysewske @Candice-Louw @JaquM @kwa20
In preparation against next Monday, I would suggest that we pick the main items here to create a very basic version that can be implemented in a sprint ie no management process module, import, etc ie just the entities + links.
In summary we would need 3 entities:
vaccinations are just "followup" of the immunization entity, thus 1 --> n
I a contact person or ep is vaccinated after their 14 day followup, then we do not need to come back and register this information to the contact. Or for someone who is neither a case, contact or ep who got involved in the immunization program of the GE.
@Candice-Louw @kwa20 just realized that having the location/ facility attached to the vaccination would make things complex. In the new issue #4756 I added the facility to the immunization. If a person is to be immunized, then there can be only one responsible jurisdiction/ facility. If a vaccine has many doses, then they must get both doses at the same facility or document one of the two as the responsible facility, hope this is fine?
@MateStrysewske @JaquM Here some comments and further specifications for this module. These cover multiple sub-issues.
Add Immunization startDate
, immunization endDate
- defines the period in which the immunization is happening until the person acquires immunization
Add ImmunizationManagementStatus
: scheduled
, ongoing
, completed
, canceled
scheduled
: current date is before the startDate OR (current date is after startDate AND number of vaccinations = 0)ongoing
: current date is >= startDate AND number of vaccinations is >= 1 AND number of vaccinations is unequal to the expected number of vaccine dosescompleted
: number of vaccination entries equals the number of expected vaccine dosescanceled
/resume
: button to cancel which enables a free text to provide a reason for cancellation; button to resume immunization if previously canceledimmunizationManagementStatus
to completed
immunizationManagementStatus
to completed
Add ImmunizationProtectionStatus
: pending
, acquired
, notAcquired
, expired
- (non-editable) determines the protection status of the immunization for the disease
pending
: If immunizationManagementStatus
equals scheduled
OR ongoing
acquired
: If immunizationManagementStatus equals completed
notAcquired
: If immunizationManagementStatus equals canceled
- has to revert back to pendingexpired
: If current date is after the validUntil
dateAdd Immunization validFrom
and validUntil
dates - defines the protection time frame of the aquired immunization; enabled when immunization equals acquired
Add the following feature configurations:
Directory refinements: -Add columns for (all sortable alphabetically):
@kwa20 have you planned to calculate the date of recovery based on the existing data in Sormas if the person was already a case? If yes, please show then the calculated dates for #5394 (for Germany only).
Closing this, since the core module is already implemented. Follow-up issues are not done yet, but are not considered part of this epic.
Pre-requisite for this to be released: #5986
Linked issues: I: Immunization entity #4756 [5] II: Vaccination entity #4763 [3] II: Immunization overview and forms #4764 [5] II: Immunization overview and forms (app) #5827 [5] III: Immunization list for person forms #5828 [2] III: Immunization list for cases, contacts and event participants #5905 [5] III: Vaccination lists and create/edit forms #5843 [3] III: Immunization automation #5946 [1] IV: Vaccination refactoring #5909 [5] V: Link recovery immunizations to recovered cases #5969 [2]
Follow-up issues: Make the Vaccine and VaccineManufacturer enums configurable #5830 Move information about vaccination being enabled to the diseaseconfiguation table #5831
Situation Description
An Immunization (consisting of various vaccinations) module (especially for COVID-19) is highly requested for SORMAS.
In order to produce a minimal viable product, as fast as possible, to support international audiences making use of SORMAS, resources from the RKI (SurvNet) [DE], BAG MED [CH], FHIR7, and CDC have been consulted in an attempt to provide a module that may possibly address basic user needs.
Feedback welcome.
There are numerous steps/components that make up this request:
Overall mockup (as on 19.01.2021)
Feature Description
1. Allow vaccines to be configured in the Configurations
Values: Vaccine name, vaccine type, vaccine code, producer, external ID
2. Introduce the Immunization module functionality [please see Overall mockup (as on XX.XX.2021) on the top of the page for the latest version pertaining to UI specifications]
3. Add Immunization details to Case, Contact and Event Participant entities
See #4137 for specifications on this element.
Allow COVID-19 to show the 'Additional medical information' box with the 'Vaccination status for this disease' box (as is existing for Measles for example for Cases right now).
4. Add Immunization details to the Person entity
Based on development of #3560 , also include Immunizations as a list element for the Person entity (viewing all Immunizations and adding/creating new Immunizations for all diseases).
Additional Information
Data mappings (as on 19.01.2021)