*FHIR Release 4 is out of scope for this proposal because addressed by John in a separate work-item.
=== Thursday, 28th February, 2019 ===
*Main Issues:
**several CPs are assigned to non-active members: retired people, or no longer active organizations
**several CPs affect profiles that could be ready for FT publication. We need to be aggressive on those CPs.
**Lack of expertise in some topics: HL7 v3, HPD, ebRIM.
*The other key topics are: MU , ATNA BCP195.
*It seems that there is less interest in participating on maintenance activities (probably due to the addressed topics...). This is also due to the retirement of some really active members (Ken, Elliott, Rob, ...).
*Lack of expertise, some CP are not moving because of retirement. Do we need to enroll new people asking Planning to do this? We should reduce distance between CAT and TECH CMTE.
*Possible solution proposed by the group: ask specific people to take on a specific CP that affect actors of interest for them (this would allow to engage in Tech activities non-active members).
*Charles raise issues about the process of engaging submitters: how call are organized and how invitations are sent out. Lynn will try to be more direct in invite people to join specific CP calls.
*Lynn, would like to ask submitters to propose also a solution not only raise the problem. This will make the CP process faster.
*DECISION: Planning decided to not dedicate time during f2f time for CP or maintenance (except for specific critical topics).
| style="text-align: left" | ''Minutes'': Joe Lamy: ''deferred XCA''
*The use-cases presented by Joe, cover two functionalities, deferred query and deferred retrieve
*A discussion is raised about deferred retrieve: it is borderline with async or if it’s indeed covering meaningful uses cases.
*There is suggestion to try to address deferred query with a combination of other profiles: it looks like we could cover the same use-case with a lightweight DSUB, or could be implemented with ad-hoc XDW workflow, that track the process of scanning of paper documents.
*Tarik: DSUB anyway is no good as it doesn’t fit the requirements to be cross-community.
*Is this end to end (involving XDS reg, Repository, XCA init, resp) ? Do we have any assumption about the communities (XDS, non-XDS) ?
*We don’t know if we need a deferred option for XDS.b as well. This will be explored later.
*we need to further explore if AS4 does not fit use-cases:
**use AS4 only for 1 transaction
**AS4-editors themselves declared that it is no good for deferred
*Vassyl declared that we could have an issue combining AS4 and Deferred because we can’t add new soap headers. So the change should be in the body part of the message.
**NO, in accordance to the technical evaluation made, there aren’t Detailed Proposals with clear unachievable technical issues.
**We identified only one blocking issue about “Enhance PIXv3” proposal: we do not have an editor for this proposal. This work-item is excluded from the prioritization.
*Also the development approach will affect the ITI Tech prioritization. The intent, as discussed during the Joint meeting, is to pilot a continuous development process. We will start from the draft of process proposed by John. We will take on new work-item as we will have some open slots (e.g. from February we will open the slot dedicated to the FHIR Release 4 updates because we will hopefully reach the publication goal as expected).
*About resources availability: the ITI tech identifies a lack of resources compared to the previous year. We need to acknowledge this. We should take on a lower total effort this year.
*The cmte has still a lot of concerns about the scope of “PIXm update with feed transaction”. It is not clear if we need to cover all the dependencies for XDS and MHD. Business problem: behavior of merging are described in some different profiles. Derek wants to see these behaviors covered in a FHIR profile, and also some other ITI members sees the importance of this proposal.
*The technical cmte agreed on taking on 2 small work-items and 2 large work-items for this cycle following the Planning prioritization.
*PIXm is moved over DSUB because of standards maturity (Subscription Resource has FMM level = 3, Patient resource goes normative in Release 4).
*Mauro moves the Motion to approve the follwing profiles for development during the 2018/2019 cycle: XCA Deferred Response Option , Facilities and Hierarchies in FHIR, Update core set of IHE-on-FHIR profiles to FHIR Release 4, Add Feed transaction to PIXm (insert, update, link/unlink, and merge) Ben second it
| id="11-16-1200" | Joint session with ITI Planning Committee
* Finalize work item selection
| style="text-align: left" | ''Minutes'': ITI Tech confirmed Planning prioritarization exept for: PIXv3 Unmerge/deletion (due to lack of editors able to work on the profile), DSUBm (due to lack of maturity of the baseline standard).
| id="11-16-1400" | TBD , more discussion about continuous development?
| style="text-align: left" |
''Minutes'':
Some additional point of discussion related to Continuous Development:
ITI Tech co-chairs will send out to Mary the publication plan next week. Related to the contnuos developpment: ITI will try to confirm 4 weeks before that we are probably publishing stuff at the end of the next f2f. John has already discussed this with Mary, but he will try to cover in detail issues related to the publication in the wiki draft.
This 5-days meeting is focused on a review of the first draft of work-items selected on November. The primary goal is to complete at least vol.1 content for each new work-item, but in some cases the Technical cmte will be able also to issue a public comment version for some profiles. Due to the agreeded scheduling the Release 4 updates have been published in public comment on January, so the goal for them will be the review of comments received.
Finally: starting from this year we are experimenting a continuous development process (as agreed by TC and PC in November) so on Friday we will review the prioritarization list of proposals submitted in october and we will decide if the TC can start the work on some of them.
Meeting Location
RSNA Building, Oak Brook, IL
WebEx information for this meeting is
Meeting Number: TBD
Password: Ask Sarah Bell (sbell@himss.org)
Link: TBD
Support material
Profile proposals and other support information may be found in the [1]