14.09.2016 Views

In this Issue HL7 News

2cndmS4

2cndmS4

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

IHTSDO and <strong>HL7</strong> <strong>In</strong>ternational Working Together • September 2016<br />

Collaborating for improved interoperability<br />

IHTSDO and <strong>HL7</strong> <strong>In</strong>ternational Working Together<br />

By Jane Millar, Head of<br />

Collaboration, IHTSDO<br />

<strong>In</strong> August 2014, IHTSDO and <strong>HL7</strong> <strong>In</strong>ternational<br />

signed a new collaboration agreement with a focus on<br />

key joint work areas to be undertaken over a two year<br />

period. Since that time, we have made progress in<br />

several areas in the steps to ensure that our standards<br />

can work together in health information systems.<br />

This progress includes the following:<br />

• We have worked together to ensure that <strong>HL7</strong><br />

<strong>In</strong>ternational developers and implementers<br />

throughout the world are aware of the<br />

licensing requirements for SNOMED CT by<br />

including licensing statements in products<br />

and providing FAQs on the topic.<br />

• To facilitate the use of SNOMED CT in <strong>HL7</strong><br />

<strong>In</strong>ternational products, developers anywhere in<br />

the world who are contributing are able to access<br />

the latest version of SNOMED CT <strong>In</strong>ternational<br />

through a portal set up by <strong>HL7</strong> <strong>In</strong>ternational.<br />

• We are in the process of finalizing a SNOMED<br />

CT Development Licence which will allow<br />

<strong>HL7</strong> affiliate countries to undertake their<br />

own development work using SNOMED<br />

CT, regardless of whether they are an<br />

IHTSDO member country or not.<br />

• <strong>HL7</strong> and IHTSDO have worked together<br />

on the content in the latest version of<br />

Term<strong>In</strong>fo, currently a Standard for Trial Use<br />

(STU), related to SNOMED CT to ensure<br />

the guidance is up-to-date and accurate.<br />

• IHTSDO has started work with the Fast<br />

Healthcare <strong>In</strong>teroperability Resources<br />

(FHIR®) leadership on defining best practice<br />

for binding SNOMED CT in FHIR profiles.<br />

This work is ongoing and we expect it to be<br />

a key component of the updated work plan<br />

currently being refined. This approach is also<br />

being applied to CIMI which is now a work<br />

group in <strong>HL7</strong>, thus maintaining consistency.<br />

• <strong>HL7</strong> has established the <strong>HL7</strong> Terminology<br />

Authority which, as a single point of contact,<br />

is responsible for dealing with any requests to<br />

IHTSDO for changes and additions to SNOMED<br />

CT as required for <strong>HL7</strong> products. This will<br />

reinforce that there is an efficient and effective<br />

process for ensuring <strong>HL7</strong> value sets have<br />

relevant and up-to-date SNOMED CT content.<br />

• <strong>HL7</strong> is undertaking a review of its value sets<br />

and IHTSDO is happy to review any SNOMED<br />

CT requirements that arise from <strong>this</strong> to ensure<br />

a smooth and timely update to value sets.<br />

Both <strong>HL7</strong> and IHTSDO have been able to explore<br />

approaches to collaboration, management of<br />

licensing and how to deal with terminology. This<br />

knowledge can be applied to other collaborations.<br />

This also feeds in to the work of the Joint <strong>In</strong>itiative<br />

Council. At <strong>this</strong> time we are exploring the next<br />

phase of joint work which will include the use of<br />

SNOMED CT in FHIR, potential opportunities<br />

for collaboration with education as well as other<br />

guidance about our standards working together. ■<br />

15

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!