Initial Use Cases proposed

[ritikarawlani]

Contact Details

[email protected]

Is your feature request related to a problem? Please describe.

Exhaustive list of Use Cases

Describe the solution you'd like

1. Holder requests generation of link
   • (the process of establishing trust will be a precondition here..., what type of link and what kind of resources you should be referencing)
2. Holder shares link (with pin or cert based)
3. Receiver accesses the link
4. Holder requests to destroy the link
5. Receiver accesses the data and updates the link and provides a new link back

It could be sharing any document aligning with Document Sharing Infrastructure - not limited to FHIR artifacts

enumerate all the needs around trust within usecase 1...what is the need that enables the receiver to trust the content, what the expectations are within the above use cases...

Describe alternatives you've considered

No response

Additional context

No response

Code of Conduct

• I agree to follow the IHE Code of Conduct

[ritikarawlani]

We can lean on the WHO use cases for Hajj to see what kinds of issues did they have to solve for. Some, no doubt have to do with a trust framework, however, practically speaking, there could be a requirement that says that the resource referenced by the link HAS to be digitally signed by the issuing organization. These are the kinds of detail that UC1 could list, for the appropriate content.

[slagesse-epic]

We should ensure that our use cases describe what is missing from SMART Health Links.

Else, we risk creating a competing standard with SMART Health Links, and creating competing standards is generally harmful for interoperability.

[AllanaCameron]

We should ensure that our use cases describe what is missing from SMART Health Links.

Else, we risk creating a competing standard with SMART Health Links, and creating competing standards is generally harmful for interoperability.

To ensure that we do not duplicate/re-define the use cases within SHL, should the IHE profile refer to SHL where they already have the use case defined? And then, in the IHE profile use case, it will expand the necessary additional pieces?

[JohnMoehrke]

Use-Case, patient can see all the times the VHL was used.

[JohnMoehrke]

• make clear that a VHL is just one document, or many.
• make clear that VHL "document" is as broadly defined as in Document Sharing, that is to say it is not purely a document according to the document principles that CDA has defined, and thus can be any stream of bytes simply following a mime-type.

[JohnMoehrke]

To what extent can the VHL expose information? Will the VHL need to be completely opaque, or can the VHL be partially understood by looking at the URL parts that make up the VHL?

[JohnMoehrke]

can a VHL have an expiration date/time? Or only be revoked?
Make clear that after revoked or expiration, the VHL can't be used, but this does not affect copies that may have been obtained from the VHL prior to expiration or revocation.

[JohnMoehrke]

does the VHL need to be compatible with SHL? I am concerned that SHL has defined their own json schema.

[litlfred]

In my opinion no, at least as a strict compatibility . The use cases are very similar (with the exception of verifiability) so I hope we can leverage relevant bits of SHL. For example, if you are thinking of the manifest, we should consider IHE manifests rather than the bespoke schema. Cheers, -carl

…

On Fri, Nov 8, 2024, 17:26 John Moehrke ***@***.***> wrote: does the VHL need to be compatible with SHL? I am concerned that SHL has defined their own json schema. — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFBVYUPVYLQFJWPGWN5YB3Z7S3XBAVCNFSM6AAAAABQO4XKUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRUG43DKMZTHE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[litlfred]

This will depend on the use case. For a example with Hajj, there is a set time for the pilgrimage in which the VHL was valid. A few weeks after Hajj they were considered expired (the buffer was added in case people stayed after Hajj for tourism). For other uses there may be no expiration. For example the planned WHO digital ICVP (yellow book) with a yellow fever vaccines would not have an expiration as yellow fever vaccine is now considered valid for the lifetime of the individual. By "not affect copies" do you mean copies of the health documents that were referenced and downloaded via the VHL? Cheers, -carl

…

On Fri, Nov 8, 2024, 17:24 John Moehrke ***@***.***> wrote: can a VHL have an expiration date/time? Or only be revoked? Make clear that after revoked or expiration, the VHL can't be used, but this does not affect copies that may have been obtained from the VHL prior to expiration or revocation. — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFBVYQNTTORRB2HQ34XFEDZ7S3QVAVCNFSM6AAAAABQO4XKUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRUG43DEMJTGM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>