I am wondering if there is a tool to create PDF forms from OpenEHR Templates. I used Ocean Template Designer to create OFD form and got it compiled and running (attached) but export somehow doesn’t work. I tried exporting in VB code as well as in C#. In addition, I also tried with XML but couldn’t figure out a way to create a full featured PDF form which can be shown to clinicians before further steps.
I also had a quick look at Better Studio and LinkEHR but couldn’t find any option. I encountered some errors while running ADL workbench so don’t know if there is an option in it. I am wondering if there are tools which provide this feature.
my understanding is that you want to automatically create a PDF form from a template. I think that’s a pretty cool idea. Unfortunately, I’m quite sure that there is no tool that can do this at the moment. The mentioned OFM format is Ocean specific and I guess will be of limited use for you.
Better’s Web Template Format or the OPT are the best starting point from my point of view. We have a tool inside our openEHR SDK that automatically creates java classes from OPTs (https://github.com/ehrbase/openEHR_SDK). Next week, my colleague will work on java docs and make the code more understandable. Combined with something like Apache PDFBox, I think it should be possible to implement such a tool. However, it might take some digging and developing on your side
Thanks for your comments. I know how to create Forms from Templates, the idea was to create “Portable Forms” from them to send it to clinicians before developing them and implementing them in a HIS. e.g. for cancers, the Forms are often dynamic and it would make more sense to have a prototype of a template as a PDF to send around and have doctors opinion about it.
@yampeku: I tried it with some archetypes and got variable results i.e. some forms (html) were more neat than others.
@erik.sundvall: No, I was talking about using them as a Prototype before implementing them.
The problem with templates (and showing them to clinicians) is that they are not app prototypes, they are datasets, and as you have noticed they can seem a but untidy, and will often not match the app requirement correctly.
I think we could do with some better template visualisations for this purpose but I suspect we might be better to go straight for form builder type prototypes, and ‘hide’ more of the necessary infrastructure.