The documentation for the ImagingStudy resource calls out the key image use case so my expectation is reasonable. The data model also supports multiple ImagingStudy resources per DiagnosticReport so it is possible to have multiple views (e.g. full study, key images, qa images, etc) - but how would a viewer determine which one to display? There is no code that can be used to determine what type of ImagingStudy this was. Figuring out which ImagingStudy to initially display would therefore require some convoluted logic that would probably be unreliable. My heart broke a bit as I encountered my first real world limitation of FHIR. Fortunately we have control over the datasets we are using in the hackathon so I have the ability to "make it work" through a variety of means. I decided I would reach out the FHIR gurus and see what they had to say:
I quickly learned that this was the wrong place for my question and I should check with the Imaging Integration working group. I also learned about HL7 FHIR DSTU 2 - the next version of HL7 FHIR that is currently being worked on which includes a new resource named ImagingObjectSelection. It seems that the new version of ImagingStudy is a manifest of the entire study and all subsets are moved into the ImagingObjectSelection. The ImagingObjectSelect has a title property which is a CodeableConcept of type KOStitle. KOStitle has around 20 different terms that can be used to give meaning to a given set of images.
One thing I can't figure out from the documentation is how the ImagingObjectSelection is related to the DiagnosticReport and ImagingStudy. It is still a works in progress so perhaps it hasn't been decided yet or just not documented. Regardless, my faith in FHIR has been restored as the folks behind it are definitely on the right track!
hi Iam pardhu. I need small information from you. I want to validate resouces on FHIR for dstu2 .Could you please provide the validator source code for visualstudio2012.
ReplyDelete