ProblemObservations are not present in ContinuityOfCareDocument if templateId for IHE PCC is present

[StanislauParuchnik]

Hi, I have a CCD R1.1 documents which have the following problem observations piece:
<observation classCode="OBS" moodCode="EVN">
    <templateId root="2.16.840.1.113883.10.20.22.4.4"/>
    <templateId root="2.16.840.1.113883.10.20.1.28"/>
    <templateId root="1.3.6.1.4.1.19376.1.5.3.1.4.5"/>

TemplateId id from IHE PCC specification (in bold) is present saying that this observation is also conformant to IHE PCC ProblemEntry and so the observation is parsed into ProblemEntry object.

I'm wondering if it makes sense that if the document object class is ContinuityOfCareDocument then observation should be parsed into ProblemObservation type defined in CCD if necessary templateId is specified disregarding other templateIds?

Sample maven project demonstrating this:
problems-demo.zip

[swmuir]

As you can tell - the determination of which corresponding template to instantiate can be complex
In general, based on what is available at run time is the first step - so if the template is unknown it is ignored, secondly we attempt to get the most constraining which works well in the 100% consolidated space as the templates build onto of each other - in this case we have two unrelated templates ids
so the right answer is arbitrary - the current framework supports the ability to add complex rules such a you are asking, would need to decide if this is a common occurrence; ultimately having "mixing" like feature that collects the constraints dynamically and fires them accordingly would be the best. At this point there is no resources for such an update to MDHT

I can point you to the code that can be modified to alter the template selection if you were interested

Thanks

Sean

[StanislauParuchnik]

Thank you Sean.

Yes, please point.