Skip to end of metadata
Go to start of metadata
Moved/SecondedLorraine Constable  / Ron G. Parker
Due date2019-08-15


Bernd refuses to withdraw (see below) , so we should decide whether to recirculate.

Recirculation form: SAIF_CANONR2_R1_N1_2019JAN

Reconciliation document:

: Bernd Blobel []
Sent: Sunday, August 04, 2019 6:48 AM
To: Julian, Anthony J.; Lynn Laakso (HL7)
Cc: Frank Oemig
Subject: [EXTERNAL] Re: Request for Withdrawal or Retraction of your Negative Vote
Importance: High

Dear Antony,

Thank you very much for informing me about the ARB WG Reconciliation outcome on Reaffirmation of HL7 Service-Aware Interoperability Framework: Canonical Definition Specification, Release 2 (REAFF_SAIF_CANONR2_R1_N1_2019JAN). Having been pushing the installation and the engagement of ARB right from the beginning - strongly impacted from my long term engagement at OMG and its experiences with an ARB - I cannot withdraw my negative vote or retract my vote altogether.

By comments didn't address the technical details of the specifications, but requested an inevitable amendment: the deployment of the ISO Interoperability Reference Architecture on top of the specs. It is impossible to interconnect ISO, CEN, etc., specifications from different domains. The same olds for almost all health informatics specifications, as healthcare is interdisciplinary by nature. The reason are the different knowledge spaces, methodologies, terminologies and ontologies the experts form those different domains necessarily deploy. Bridging between them mutually would turn back to the time before the HL7 communication standards have been introduced, resulting in endless revision cycles and inconsistent specifications. The ISO Interoperability Reference Architecture - compliant with as well as enhancing the OMG CIM approach - is meanwhile adopted not just by ISO and CEN, but also by IEEE or ISO/IEC JTC1 projects, doesn't replace the technical specifications of the SDOs, but enables the correct and consistent selection, constraining, profiling and completing of existing specs. Such tool is inevitable for especially approaches like the HL7 Service-Aware Interoperability Framework and therefore cannot be ignored. Even HL7 specifications addressing multiple-domains business cases such as newest SOA specs HL7 XParadigm model transformation service or the HL7 Common Security and Privacy DAM and other security specifications have acknowledged that Interoperability Reference Architecture and integrated the approach.

I'd be ready to discuss the details for properly managing this approach also in the ARB context in a video call at any time.

I put Frank as former Affiliate Director and CTO at HL7 Germany in CC.

Very best regards,


Action items