1st eStandards conference: next steps for standardization in large scale eHealth deployment: Tools for the lifecycle of standards

Next steps for standardization in health information sharing

Tools for the formal standards life-cycle

HL7 International

Foundation

April 21st, 2016 eStandards Workshop at conhIT 2016, Berlin 1

THE ROLE OF THE TOOLS IN STANDARDS-DRIVEN EHEALTH INTEROPERABILITY

Giorgio Cangioli HL7 Int. Foundation


Premise

• Out of scope – Why standards are needed for assuring “all-level”

interoperability


[Refined eHealth European Interoperability Framework]

[Australian E-health Interoperability Framework]

The need for standards set (using an architectural approach)

• Standard-based services deployment requires an architectural approach considering several interacting aspects.

• A portfolio of standard artefacts has to be in general used.


• Effectiveness and efficiency are strongly impacted by solutions (including tools) enabling the adoption of the selected standards and their cooperative usage

The standard and the deployment lifecycles


Requirements / Vision Design

Development / Procurement

Testing Deployment

Maintenance

Two interplaying lifecycles……


Standards Deployment


….with cooperating actors

• A portfolio of tools for supporting each lifecycle…..



• …. facilitating their interaction …


…support the different needs of the actors …and facilitate their communication


SDOs

SROs

SMEs

…..

CxOs

Architects

Vendors

HCOs

….

Standards has changed (and are changing)

• Model driven approach • From text-based (paper, excel, pdf) to

computable artefacts (e.g. models) • All become computable (HL7 FHIR®)

– Profiles/Templates – Implementation Guides – Test Scripts – ….


Standards has changed (and are changing)

• User adapted information – Each type of human or non-human user needs

different types of information and artefacts. – The format shall be understandable and shall fit

for each purpose


Tools may assure the consistency between the published human readable (html, pdf,….) and computable artefacts

with the reference standards and/or profiles.

The combination of tools and standard formats


Less Costs

Better Management

Less Ambiguities

Improved Access &

Reuse

Easier Validation

Tools Standards

Computable Formats

So that ?

• SDOs / SROs should promote tools that – Are designed to facilitate the adoption of

(portfolios of ) standards by users (not only for standards developers!)

– work seamlessly within and across the different phases of the lifecycles (development, publication, test, implementation & deployment, maintenance…).

– Rely on open and standards formats (hopefully harmonized standards…)


So that ?

• Potential users should be made aware about the tools capabilities. – HL7 Europe will host a registry of tools for eStandards.

• The effectiveness of tools should be monitored !


A draft for comments registry is currently available

http://wiki.hl7.eu/index.php?title=Tools

http://wiki.hl7.eu/index.php?title=Tools

Standards-related tools …

• … are essential for supporting standards-driven eHealth interoperability ..

• … are not just for standards developers… • … should use open (hopefully common) standard

formats, to better support the cooperation between the standard and the deployment lifecycles…


.. to make the use of standards more cost-effective and enable sustainable investments in eHealth !

Thank you for your attention


www.estandards-project.eu

Health & Medicine

1st eStandards conference: next steps for standardization in large scale eHealth deployment: Tools for the lifecycle of standards