Difference between revisions of "ITI Planning - 20180918"
Jump to navigation
Jump to search
(→Agenda) |
JohnMoehrke (talk | contribs) (→Agenda) |
||
Line 16: | Line 16: | ||
* Other item proposals already mentioned: ATNA and maintenance of the documentation with FHIR R4 | * Other item proposals already mentioned: ATNA and maintenance of the documentation with FHIR R4 | ||
* Wiki pages and the roster (Lynn's recent message) | * Wiki pages and the roster (Lynn's recent message) | ||
+ | |||
+ | ===Potential New Work Items - not proposed=== | ||
+ | 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 | ||
+ | ** 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 +??? | ||
+ | * FHIR Maturity for MHD and other profiles -- some of the FHIR resources are not being naturally matured, where as IHE may be the best organnization to focus on that (e.g. MHD) | ||
+ | * 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 -- | ||
+ | * 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? | ||
==Minutes== | ==Minutes== |
Revision as of 08:00, 18 September 2018
back ITI Planning Committee 2018/2019 Meetings
Location
To join this meeting
Time 11:00 am - 12:30 pm Monthly on the third Tuesday
Go to https://himss.webex.com/himss/j.php?MTID=me852e7ebefb69e608eea3547ddceeb94
Agenda
- MoU between IHE and DirectTrust
- Upload of the summary of Lisa's item proposal on the wiki
- The wiki page of the co-chair duties (draft word version)
- Lynn's item proposal: Maintenance of ITI Profiles Published in 2018 and earlier
- Other item proposals already mentioned: ATNA and maintenance of the documentation with FHIR R4
- Wiki pages and the roster (Lynn's recent message)
Potential New Work Items - not proposed
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
- 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
- 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
- FHIR Client security -- package up the requirements for a FHIR Client to be secure. Subset of ATNA without client side cert + IUA +???
- FHIR Maturity for MHD and other profiles -- some of the FHIR resources are not being naturally matured, where as IHE may be the best organnization to focus on that (e.g. MHD)
- 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 --
- 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?