MnM's responsibility for methodology has always been limited to v3 and FHIR methodology.  It had no involvement in v2.  (v2 methodology is handled by InM.)  The CDA portion of v3 methodology is now covered by Structured Documents.  EHR-FM and other products don't have a formal methodology group and have certainly never been under the guidance of MnM.  At this point, there is no further activity on v3 messaging methodology and there won't be.  If someone had come forward over the last few years and asked for an update to v3 methodology, MnM would have said 'no' as doing so would not have been an efficient use of HL7 standards development resources.  (The interoperability 'bang' that might have resulted would not have been worth the investment by the organization.)

Given that v2 methodology is handled by InM and CDA methodology is handled by Structured Documents, having FHIR methodology handled by FHIR-I seems both consistent and appropriate.  As well, methodology for all of thesse families is largely stable, so having a work group that *only* handles methodology would not involve the level of effort/engagement that would sustain a health work group (even if it made sense to try to combine methodology for all product families together - something that seems a questionnable notion given the vast differences in approach and expertise involved).  If/when HL7 introduces a new product family, it might well make sense to have a separate group for managing methodology issues when the product is in the development/early adoption phases.

Lloyd McKenzie (he/him/his)

Management Consulting Principal Director -  Healthcare Standards


Email: lloyd.mckenzie@accenture.com
Mobile: +1-587-334-1110 

CONFIDENTIALITY – This communication is confidential and for the exclusive use of its intended recipients. If you have received this communication through error, please notify the sender and delete the message without copying or disclosing.

REPRESENTATION –  Unless explicitly stated otherwise, the opinions and positions expressed in this e-mail do not necessarily reflect those of my employer, my clients, nor the organizations with whom I hold governance positions



On Tue, Nov 1, 2022 at 8:56 AM CGIT - HL7 ListServ <cgit@lists.hl7.org> wrote:
Oemig, Frank hl7@oemig.de sent this message to cgit@lists.hl7.org
-------------------------------------------------
hello all,

we have tried to discuss the request to merge MnM with FHIR-I. Unfortunately, we (Rob and I) did not have quorum. But we can provide the contents of the discussion that is documented in confluence for our today's call:

MnM has universal applicability and needs to be independent of any one product family. In general, a lot of the WGs fall into this category and should remain, e.g. Conformance. Assimilating infrastructural workgroups into a particular product family is not an optimal long-term strategy for HL7 (as new standards will surely emerge). It is our opinion that such WGs should remain independent.

Due to the tight timeline we have to convey a vote via email.

The Motion is to disagree with proposal as is.

So please return your vote to the list and/or me and Rob asap so that we can document that.
thx

best regards
Frank

--
Diese E-Mail wurde von AVG-Antivirussoftware auf Viren geprüft.
www.avg.com

***********************************************************************************
Reply and Reply-All will most likely send to the list. Please verify address fields before sending!

Manage subscriptions - http://www.HL7.org/listservice
View archives - http://lists.HL7.org/read/?forum=cgit
Unsubscribe - http://www.HL7.org/tools/unsubscribe.cfm?email=lloyd@lmckenzie.com&list=cgit
Terms of use - http://www.HL7.org/myhl7/managelistservs.cfm?ref=nav#listrules