-
Notifications
You must be signed in to change notification settings - Fork 13
Verifiable Health Links #215
Copy link
Copy link
Open
Labels
Dev-LDevelopment effort is LargeDevelopment effort is LargeReview-LCommittee Review effort is LargeCommittee Review effort is LargeTesting-LTesting Plan Development is LargeTesting Plan Development is Large
Metadata
Metadata
Assignees
Labels
Dev-LDevelopment effort is LargeDevelopment effort is LargeReview-LCommittee Review effort is LargeCommittee Review effort is LargeTesting-LTesting Plan Development is LargeTesting Plan Development is Large
Type
Projects
Status
In development by Tech
https://github.com/IHE/IT-Infrastructure/blob/master/Proposals/IHE_Profile_Proposal_SharingVerifiableHealthLinks.docx
There are many upcoming business use cases that need to generate, share and retrieve content from Verifiable Health Links.
WHO’s IPS for Pilgrimage, Canada’s implementation in New Brunswick and more upcoming use cases, are leveraging the exchange of Patient Summary using a Person-Mediated Access approach that exchange data using QR codes embedded with Verifiable Health Links.
The transactions needed to generate and access the Verifiable Health Links and the corresponding clinical data, can be included in an integration profile within the IHE ITI domain to create a consistent approach across various implementations that can be tested for compliance.
The new integration profile can also evolve to potentially include cross-profile considerations of grouping Verifiable Health Links with other standards and profiles such as MHD for document exchange, PCF/BPPC for consent, or digital signatures for added security.