We don’t record the number of visits. Each visit is recorded as an encounter, so no need to record the number of visits. The only situation where we record multiple occurrences of an event – collecting the chemotherapy cycle number (question/numeric).
Wondering if you are anticipating the addition of two more members: 1) vaccination lot number and 2) vaccination lot expiry date in order to comply (at least in part) with ‘The Drug Supply Chain Security Actand 2D Vaccine Barcodes’ (CDC ref. here) and to enable “tracking and tracing”.
@mksd Yes. It would be easy to modify the convset to include lot number and expiration date.
If you look at Immunization History (CIEL:1421) concept, it already includes lot number, and manufacturer. @akanter might consider adding the lot expiry date to the same construct, unless this would be modeled differently with the lot number as a key to other data (expiry date and manufacturer).
As for CIEL:984, it doesn’t need to be class=ConvSet, but that’s how it is in CIEL, but it works with coded datatype. I would have made it class=Drug.
As @mksd has mentioned in the above messages, capturing Vaccine Expiry date is mandatory to be in comply with ‘ The Drug Supply Chain Security Actand 2D Vaccine Barcodes ’ (CDC ref. here). Could you help us with this to add Vaccine Expiry date to add IMMUNIZATION HISTORY concept?
I only created it yesterday It will be in the next CIEL release which is probably in a week or so. That will not likely be posted as quickly to OCL until we work on that process, but should be able to be in dropbox. If you need it now, you can create it using the information in the screenshot. The UUIDs also follow the pattern of the other CIEL terms.
Adding a next immunization date is interesting. However, its not so simple. Happy to have a separate conversation about this. However, the calculation of the next immunization is based on the specific component and not necessarily the exact same immunization that was provided previously. Also changes in the patient might change the window. We have done work in the past where we stored a text version of the recommendations based on series and put it in the Immunization Recommendation concept. I’d ask the community whether it makes sense to store this in the immunization history on a line by line basis. @paul as a pediatrician, what do you think?
Sorry for adding one more conversation in between. I have found this thread might be suitable for this question.
As part of our existing work related to Immunization History, we want to capture the name of the vaccine which is not available in Immunizations (5622) list (For ex. Corona).
Immunizations allows us to choose Other ( 5622) when do not have the vaccine in our list. But we do not have a concept like Other Vaccine Name to capture that vaccine name (Corona) which is not available in the list.
Please share your thoughts about adding a new concept to capture Other Vaccine Name to IMMUNIZATION HISTORY (1421)? or do we have any other option to capture the same.
Sorry, I missed this. I would prefer to add any immunization to the database because for immunization monitoring to work properly there needs to be properly documentation (including CVX codes). It would be possible to include Other Vaccine Name (Text) to history, but it will be non-standard and would not be recommended to use. For COVID-19, I would prefer to include that in the database if people are actually using one.