https://medplum.com logo
Join Discord
Powered by
Questionnaire Translation
# support
t
Hello @medplum team. I have a quick question concerning questionnaire translation. After chatting on chat.fhir.com I have tried to use an extension that is the following https://build.fhir.org/ig/HL7/fhir-extensions/StructureDefinition-translation.html When trying to implement the json described i have the error that you can see in the enclosed image. How would you recommend to handle translation ?
It looks like the correct usage is to add a new property like "_text" on which we will add new extension Does that make sense to you @rahul1 ? Did you already have to handle this use case on Medplum ? I'm wondering because it looks like Medplum is not happy witht he _text property. When trying it on the FHIR validator, I don't have any error because of the new "_text" property. If you have informations on this I'm happy to hear about it 😉
d
Hi, I've been adding extensions to questionnaire.items. adding an extension to the item should work, 
_text
would be discouraged. do you have more info on the error you got? is very vague
t
Hi @dvidsilva Where did you see that _text is discouraged ? On Medplum that is the only error I've got ! I just have the error on the timeline though, I don't have any error when displaying the questionnaire in the builder or other page. How did you wrote your extension ? Was it one your created or one you found ?
d
Adding any new property can interfere with type checking and interoperability. The extension property is encouraged
I made my own extension urls and added arbitrary data that I want https://dev.lotuscares.ai/api/extensions/form_id
r
Hi @thomabig , thanks for your patience here. there are a few different parts of this post. - For general guidance on internalization, check out my response here: https://discord.com/channels/905144809105260605/1254903986633572433 - For general resources, you can use the 
translation
extension - For "knowledge resources" (e.g. Questionnaire), the "language" element is preferred
Regarding 
_text
- the 
Resource.text
field is generally a narrative summary of the resource, but doesn't really have operational usage - Any "primitive" element can have extensions added by using the 
_<element_name>
syntax - That's what's going on with 
_text
Agree with @dvidsilva that it doesn't seem like the most direct way to store what you want here
As for the UI issue, I think this might just be an issue with the Medplum App UI, so feel free to file a Ticket and we can take a look
176 Views
PreviousNext
Powered by