The Standard

The Official Blog of Health Level Seven® International

visit HL7.org 

5 Ways to Market Yourself With HL7 Certification

[fa icon="calendar'] Aug 21, 2018 4:37:40 PM / by Sadhana Alangar, PhD posted in FHIR, HL7 education, CDA, certification, Version 2, Version 3

[fa icon="comment"] 0 Comments

Are you HL7 certified?

HL7 offers certification in its primary standards for health information technology including Version 2 (V2), Version 3 (V3), Clinical Document Architecture (CDA®) and HL7 Fast Healthcare Interoperability Resources (FHIR®). The testing is designed to help professionals achieve industry-recognized levels of proficiency and expertise.

Read More [fa icon="long-arrow-right"]

The HL7 Fundamentals Course is Fundamentally Different

[fa icon="calendar'] Aug 3, 2018 11:07:26 AM / by Sadhana Alangar, PhD posted in FHIR, HL7 education, HL7 Affiliates, CDA, HL7, Version 2, interoperability, Version 3

[fa icon="comment"] 0 Comments

A Little About HL7

Read More [fa icon="long-arrow-right"]

Is HL7's FHIR Ready To Revolutionize Interoperability in LATAM? Is LATAM Ready for FHIR? Part 1

[fa icon="calendar'] Sep 28, 2016 9:54:40 AM / by Diego Kaminker posted in FHIR, CDA, HL7, HL7 community, Version 2, Latin America, interoperability

[fa icon="comment"] 0 Comments


 
A little history

Studying HL7 history, our standards went from a plain text, replication/messaging-based paradigm in the 1980s to the current, Internet 2.0, resource-based paradigm. We also created document-based standards such as the Clinical Document Architecture (CDA®) Release 2 and SOA based standards like Common Terminology Services (CTS).

These 30 years of history gave us a good insight on what we need as standards users and developers.

What do we need as standards users?

People who implement and use standards want open access to standards and implementation guides. They need understandable and short specifications, off-the-shelf tools, reference implementations, friendly representation of information (instances), easy access to vocabularies, automated validation of instances, affordable education, a formal extension mechanism. 

Finally, they need examples, examples, and more examples. They need lots of examples!

What do we need as standards developers?

Standards developers have different needs. They want easy profiling with graphical user interfaces (GUI) and the ability to reuse templates. They also want one-click, automated publishing, validation and QA profiles, validation of instances, global profile registry, and ease of vocabulary binding.


Read More [fa icon="long-arrow-right"]