Principal Results Interpreter comes from the HL7 field that transports this value, so I figured it was a typical medical term for specifically noting the “author” of a report. I don’t a huge preference of that over author.
Bigger question though–would it make sense to try to migrate RadiologyReport (and other domain objects) from RadiologyApp module into the Radiology module, rather than have two separate “Report” modelling?
difference is we have a report status. So a user can claim reporting an order once the order is complete and has a study with images. This ensures no one else will report the same study. The report is than in status claimed and the user can edit as long as he wants, like a draft. Once the user is happy with it he puts the report into status complete.
We also dont have any concept members. The imaging procedure is stored with the RadiologyOrder as concept and we dont have a report type so far.
I dont think we can simply migrate RadiologyReport and your other domain objects with the features we (@judy) have currently in mind. Not sure what the best way would be to go about this.
@mogoodrich I think we would need to find a common ground for the functionality we want the module to have and see what of the existing domain objects, services from the radiology app should go into the radiology module and what changes would need to be done in the radiology app.
If you would like we could create a radiology task force/design group?
currently we have a lot of helping hands who want to get started, so we would need to decide soon on how to proceed. otherwise I guess the modules will diverge. @judy wants to deploy it in Malawi in June which is soon and we havent released the module yet since it still lacks stability and features.
@jthomas I have a family emergency and cannot make it. I am very sorry but I need to cancel the meeting. Can you please make sure everyone knows. Thanks a lot!!!