The genotype list string code syntax for exchanging nomenclature-level genotyping results in clinical and research data management and analysis systems.

The nomenclatures used to describe HLA and killer-cell immunoglobulin-like receptor (KIR) alleles distinguish unique nucleotide and peptide sequences, and patterns of expression, but are insufficient for describing genotyping results, as description of ambiguities and relations across loci require terminology beyond allele names. The genotype list (GL) String grammar describes genotyping results for genetic systems with defined nomenclatures, like HLA and KIR, documenting what is known and unknown about a given genotyping result. However, the accuracy of a GL String is dependent on the reference database version under which it was generated. Here, we describe the GL string code (GLSC) system, which associates each GL String with meta-data describing the specific reference context in which the GL String was created, and in which it should be interpreted. GLSC is a defined syntax for exchanging GL Strings in the context of a specific gene-family namespace, allele-name code-system, and pertinent reference database version. GLSC allows HLA and KIR genotyping data to be transmitted, parsed and interpreted in the appropriate context, in an unambiguous manner, on modern data-systems, including Health Level 7 Fast Healthcare Interoperability Resource systems. Technical specification for GLSC can be found at https://glstring.org.

Modeling and validating HL7 FHIR profiles using semantic web Shape Expressions (ShEx).

BACKGROUND: HL7 Fast Healthcare Interoperability Resources (FHIR) is an emerging open standard for the exchange of electronic healthcare information. FHIR resources are defined in a specialized modeling language. FHIR instances can currently be represented in either XML or JSON. The FHIR and Semantic Web communities are developing a third FHIR instance representation format in Resource Description Framework (RDF). Shape Expressions (ShEx), a formal RDF data constraint language, is a candidate for describing and validating the FHIR RDF representation. OBJECTIVE: Create a FHIR to ShEx model transformation and assess its ability to describe and validate FHIR RDF data. METHODS: We created the methods and tools that generate the ShEx schemas modeling the FHIR to RDF specification being developed by HL7 ITS/W3C RDF Task Force, and evaluated the applicability of ShEx in the description and validation of FHIR to RDF transformations. RESULTS: The ShEx models contributed significantly to workgroup consensus. Algorithmic transformations from the FHIR model to ShEx schemas and FHIR example data to RDF transformations were incorporated into the FHIR build process. ShEx schemas representing 109 FHIR resources were used to validate 511 FHIR RDF data examples from the Standards for Trial Use (STU 3) Ballot version. We were able to uncover unresolved issues in the FHIR to RDF specification and detect 10 types of errors and root causes in the actual implementation. The FHIR ShEx representations have been included in the official FHIR web pages for the STU 3 Ballot version since September 2016. DISCUSSION: ShEx can be used to define and validate the syntax of a FHIR resource, which is complementary to the use of RDF Schema (RDFS) and Web Ontology Language (OWL) for semantic validation. CONCLUSION: ShEx proved useful for describing a standard model of FHIR RDF data. The combination of a formal model and a succinct format enabled comprehensive review and automated validation.