|
|
| (55 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| | The IHE ITI domain has received work items proposals to be developed, see https://github.com/IHE/IT-Infrastructure/projects/2 |
|
| |
|
| | Some of them have been already selected to be developed, see [[Current development]]. |
|
| |
|
| | Others have been assessed and they are stored in this present page for a further selection. |
|
| |
|
| | The other work items proposals received are available on the [[Under assessement by planning]]. |
|
| |
|
| | The item proposals are available on the [https://drive.google.com/drive/u/0/folders/13pSEFTaiXSS2W63o7F2lxGzeuP0YEeWZ google drive] |
|
| |
|
| | | The list of potential new work items is given for information. |
|
| |
|
| __TOC__ | | __TOC__ |
|
| |
|
| =Add RESTful capabilities to DSUB=
| |
|
| |
| This proposal is in line with the work already carried out for Mobile access to Health Documents (MHD) with XDS on FHIR, in searching and retrieving documents through RESTful capabilities. This work item consists of studying how to subscribe or unsubscribe, from a mobile application, in order to receive notifications when a clinical document has been created. This work will be achieved in adding restful capabilities to the Document Metadata Subscription profile (DSUB).
| |
| <br />
| |
| <br />
| |
|
| |
| =Add restfull feed to ATNA=
| |
|
| |
|
| This proposal is in line with the work already carried out for example, for Mobile access to Health Documents (MHD) with XDS on FHIR, in searching and retrieving documents through RESTful capabilities. This work item consists of auditing the access to clinical documents from mobile applications implementing this kind of new profiles for mobile.
| | =mCSD Provider Directory alignment with Argonaut, Sequoia, and DirectTrust= |
| This work could be achieved in using FHIR, which offers the ability to POST the AuditEvent resource that is suitable to manage the audit of an event.
| | Description, see https://github.com/IHE/IT-Infrastructure/blob/master/Proposals/IHE_ITI_Proposal_mCSD_Provider_Directory_Alignment.docx |
| <br />
| |
| <br />
| |
|
| |
|
| =Enhance ITI-44 and ITI-46 transactions (PIXv3 Feed and Update Notification) to support also patient delete/deactivation and unmerge=
| | '''Assessed by Planning committee: April,22 2020''' |
| The purpose of this proposal is to respond to real-life scenarios in which patient data must be deleted or merged.
| |
| This work item consists of enhancing the Patient Identity Feed HL7 V3 [ITI-44] and PIXV3 Update Notification [ITI-46] transactions by developing Delete and Merge options.
| |
| <br />
| |
| <br />
| |
|
| |
|
| =Alignment of XDM/XDR with the DirectTrust implementation guide for representing Message Context=
| | '''Deferred for current development (need more participation of stakeholders): May 6, 2020''' |
|
| |
|
| This work item proposal has two main aims:
| | =Federate MHDS using FHIR including Patient and User federation= |
| *Analyzing the gaps between the current IHE XDR/XDM specifications and the Implementation Guide for Message Context developed by the DirectTrust community. This review effort will enable to identify and issue recommendations of merging, or (at least) converging possibilities between the two set of specifications.
| | Description, see https://github.com/IHE/IT-Infrastructure/blob/master/Proposals/IHE_ITI_Proposal_MHDS_Federation.docx |
| *Applying the changes identified to the IHE XDR/XDM specifications while extending the perimeter of the uses cases covered to fully take in consideration the use of Direct Secure Messaging (DSM).
| |
| The work item suggests that this effort will optimize interoperability by reducing the number of implementation options.
| |
| <br />
| |
| <br />
| |
|
| |
|
| =Potential New Work Items - not proposed=
| | '''Assessed by Planning committee: April,22 2020''' |
| The following is a list of things that have been spoken about, but for which we have not received a formal new work item proposal
| |
|
| |
|
| * XDM on FHIR -- usecases from XDM, but where the encoding of the metadata is using FHIR structure
| | '''Not selected yet by Technical committee for current development: May 6, 2020''' |
| ** Could extend to carrying non-Document resources on portable media
| |
| ** https://chat.fhir.org/#narrow/stream/65-ihe/topic/FHIR.20based.20XDM
| |
| * MHD asynchronous -- usecases from MHD, but where there is a need for asynchronous. Such as MHD as an API to XCA where the asynchronous MHD would allow for non-blocking
| |
| ** https://healthcaresecprivacy.blogspot.com/2018/09/improving-document-exchange-response.html
| |
| * ATNA FHIR Audit Client -- (Rob's proposal from last two years). Simply document how a FHIR Client would use AuditEvent to log the same security events as ATNA does today
| |
| ** https://chat.fhir.org/#narrow/stream/65-ihe/topic/ATNA.20on.20FHIR
| |
| * FHIR Client security -- package up the requirements for a FHIR Client to be secure. Subset of ATNA without client side cert + IUA +???
| |
| * SMART-on-FHIR usecases -- authorization of application space, specification of OAuth scope, specification of OAuth interaction (beyond IUA has today)
| |
| ** SMART-on-FHIR is about to be published as normative STU from HL7
| |
| ** Must deal with SMART-on-FHIR overlap. Is there anything to profile? Can we just reference SMART?
| |
| * FHIR Maturity for MHD and other profiles -- some of the FHIR resources are not being naturally matured, where as IHE may be the best organization to focus on that (e.g. MHD)
| |
| ** DocumentReference and DocumentManifest -- need IHE to help them progress through the FMM levels.
| |
| ** DocumentManifest needs introduction, scope, etc
| |
| ** Both need testing proof etc.
| |
| * MHD On-Demand -- document how MHD would support On-Demand -- where backend is XDS, where backend is XCA, where backend is native FHIR
| |
| * PAM on FHIR -- all of the PAM use-cases in FHIR form
| |
| * Re-Document ITI-18 -- simplify, clarify, various items Thing ONE
| |
| * Re-Document MU -- now that we have RMU, what would MU look like if we re-started today? Might it be a standalone profile rather than options on XDS? Might it be updates to RMU?
| |
| * Work more closely with PCC and QRPH to align their newest work with ITI
| |
| * Work toward a more continuous release structure vs the yearly schedule we now have
| |
| * Profiling of CDS-hooks for specific clinical usecases. Or does this become a clinical domain responsibility (PCC, etc)
| |
| * Provider Directory maturity
| |
| ** Alignment with Argonaut
| |
| ** Alignment with Sequoia Directory
| |
| ** Alignment with DirectTrust.org Directory
| |
| * Overall alignment of our FHIR profiles with Argonaut and/or Da Vinci
| |
| * Add in Sequoia - CareQuality -- Point-of-Care Consent mechanism to XCPD and XCA
| |
|
| |
|
| = See Also = | | = See Also = |
The IHE ITI domain has received work items proposals to be developed, see https://github.com/IHE/IT-Infrastructure/projects/2
Some of them have been already selected to be developed, see Current development.
Others have been assessed and they are stored in this present page for a further selection.
The other work items proposals received are available on the Under assessement by planning.
The item proposals are available on the google drive
The list of potential new work items is given for information.
mCSD Provider Directory alignment with Argonaut, Sequoia, and DirectTrust
Description, see https://github.com/IHE/IT-Infrastructure/blob/master/Proposals/IHE_ITI_Proposal_mCSD_Provider_Directory_Alignment.docx
Assessed by Planning committee: April,22 2020
Deferred for current development (need more participation of stakeholders): May 6, 2020
Federate MHDS using FHIR including Patient and User federation
Description, see https://github.com/IHE/IT-Infrastructure/blob/master/Proposals/IHE_ITI_Proposal_MHDS_Federation.docx
Assessed by Planning committee: April,22 2020
Not selected yet by Technical committee for current development: May 6, 2020
See Also
- --