-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
section.title in Composition profile should be 0..1 #105
Comments
Guess it makes sense since the code is optional as well |
The May 2024 Connectathon Track Report includes this statement: I agree that the main, first-level section should have a title. This is what the path "Composition.section.title" suggests. We should, however, not generally require all sections to have a title. There is sometimes text between identified subsections in real-world package leaflets, so we need uncoded sections. These text blocks often do not have titles either. |
Hi Adam, FDA's terminology has what's called 42229-5 | SPL UNCLASSIFIED SECTION. This allows manufacturers to add custom headings that are still encoded but they can make up any title they like. Recommend EMA do something similar. |
There are fewer examples than I thought. Going through the sections coded "unspecified", most do have a title. Some that do not could probably be merged into previous sections. For example, in https://www.felleskatalogen.no/medisin/pasienter/pas-ramipril-actavis-actavis-563214 should "Hvis barn har fått i seg legemiddel ved uhell kontakt lege, sykehus eller Giftinformasjonen (tlf. 22 59 13 00)." ("if children accidentally take X") be a part of section "if you take more X than you should"? We have them coded separately now, which leaves this text without a proper title. The examples below are the ones closest to not having a title: In https://www.felleskatalogen.no/medisin/pasienter/pil-inuxair-chiesi-farmaceutici-560226, section 3, the last identified subsection is "Dersom du avbryter behandling med Inuxair" - SPOR 200000029909, "If you stop <taking> <using> X". Before section 4 - SPOR 200000029910, "4. Possible side effects", there are several smaller sections. We have them coded together in an "unspecified" section, and collectively they do not have a single title. Maybe these should be coded in separate sections, and then "Dersom pusten din blir verre:", "Dersom astmaen blir verre:", etc. would be titles. In https://www.felleskatalogen.no/medisin/pasienter/pil-fiasp-fiasp-flextouch-fiasp-penfill-fiasp-pumpcart-novo-nordisk-649184, "Tre enkle tiltak som kan hjelpe for å unngå lavt eller høyt blodsukker er:" is between SPOR sections 200000029908 "If you forget to <take> <use> X" and 200000029909 "If you stop <taking> <using> X". Here I am unsure if "Tre enkle tiltak som kan hjelpe for å unngå lavt eller høyt blodsukker er:" is a title, or rather part of the text. In https://www.felleskatalogen.no/medisin/pasienter/pas-buventol-easyhaler-orion-547177, |
@adamzkover, In each example there would be the official EMA heading and then if EMA added a code for "UNCLASSIFIED SECTION" then we all could add whatever sub-sections beneath the official heading and title it whatever we want. if you take more X than you should <- EMA SPOR heading
|
We have a good candidate for a subsection title in the first example, that is true. The other examples are not that obvious. Example 4 with Buventol has only a single sentence in that unspecified subsection, and that text doesn't sound like a title. Most unspecified subsections will probably have a title. It would be good however to have the possibility to encode cases where there is no text that could be interpreted as a title. If not for authoring new ePILs in the future, then at least for encoding existing ones to FHIR. |
Pushed the merge earlier. Does that make it optional now? |
Yes, section.title is optional on http://build.fhir.org/ig/HL7/emedicinal-product-info/StructureDefinition-Composition-uv-epi.html now. |
Some package leaflets have unidentified sections between known subsections. These text blocks do not always have titles.
Consider making the title optional or mandatory only on the first level.
The text was updated successfully, but these errors were encountered: