Stream: IPA
Topic: docref
Jens Villadsen (Dec 23 2021 at 10:25):
@Mikael Rinnetmäki how does the IPA $docrefoperation differ from the IPS $summarythat we have discussed @Rob Hausam ?
Mikael Rinnetmäki (Dec 23 2021 at 11:00):
@Jens Villadsen obviously, the name is different. :P
The $docref is named as it is, as such an operation already exists in the US Core and we can just reuse it. The functionality, as specified in the base level IPA specification is that the operation returns an undefined default document when called without specifying a type, but you can also request documents with a profile definition, in which case you get a document based on the specified profile, if such a document exists or if the server can construct it.
Jens Villadsen (Dec 23 2021 at 11:12):
So the need for the "doc extraction operation" is present in US Core, IPA and IPS. Shouldn't it then either be extracted to its own IG, or hoisted to the global standard?
Mikael Rinnetmäki (Dec 23 2021 at 11:17):
I guess from IPA perspective we are a kind of extracting it from the US Core to a more generic specification.
I don't think it would be a problem for for IPA to refer to another IG or the base FHIR specification if it was further extracted.
I'm not sure which are the differences between the US Core $docref operation and the IPS $summary operation.
I have also seen $everything proposed, and we discussed that in IPA too.
John Moehrke (Dec 23 2021 at 13:03):
I would prefer a modular approach, where the operation to generate an IPS be defined in a purpose specific IG. It could use IPA to access the data, and it would produce an IPS compliant document.
John Moehrke (Dec 23 2021 at 13:05):
I think one of the visions of two different operations is that one would purely create the IPS, and a second would use that first one to create the IPS and also create a DocumentReference instance for that newly created IPS Bundle. Thus if you simply wanted the IPS and had no use for a DocumentReference you could get that, but if you needed the IPS you created to be discovered in the future (persisted) then you would need a DocumentReference instance created for that.
Jens Villadsen (Dec 23 2021 at 15:44):
I proposed $summary to IPS (https://github.com/HL7/fhir-ips/pull/15/files) as a broadspectered approach, where one of the input parameters would be a profileURI, in order to determine and leave it to the specific IG to figure out what the summary should consist of. As such, the $summaryoperation may have been initially defined in IPS, but is not tailored to it.
Vassil Peytchev (Dec 23 2021 at 16:25):
A very interesting discussion. My initial view of this is as follows:
$everythingreturns a graph of resources. It is defined in the core spec, and IGs must constrain it for their use$summaryimposes a (almost?) tree-like structure on top of the generic graph of resources via the rootCompositionresource. IPS is the first to use it, it is not clear to me if a more generic use case exists.$docrefcauses a DocumentReference resource to be returned (whether pre-existing , or newly created) containing or referencing a patient-specific document of some kind. My preference is that it is defined in IPA (without any restrictions on the kind/type of document), and correspondingly constrained in IPS (document is an IPS FHIR Document or IPS CDA), US Core (Document is C-CDA) and others.
I think IPS needs both $summary and $docref - they are complementary, but serve different purposes.
John Moehrke (Dec 23 2021 at 17:08):
I agree, that is what I was viewing as the modular approach.
John Moehrke (Dec 23 2021 at 17:08):
I think the additional discussion is.. where should each of these be defined. as where they are defined drives their reusability.
John D'Amore (Dec 23 2021 at 18:02):
I appreciate the feedback from above. I have been working on a page (should finish in next two weeks) with initial documentation around how to generate an IPS for the IPS IG. Here is the early draft which is currently on a branch: https://github.com/HL7/fhir-ips/blob/generation-and-data-inclusion/input/pagecontent/ipsGeneration.md I will attempt to integrate some of the above as I work on during holidays. Additional feedback welcome.
Last updated: Apr 12 2022 at 19:14 UTC
