Is HL7 FHIR Specification suitable to be added as a new project?

CLOSED This issue is closed by Nemo_bis

Unneded, until further notice

Hi Nike,

Fast Healthcare Interoperability Resources (FHIR, pronounced "Fire") is a standard for exchanging healthcare information electronically. It defines a set of "Resources" that represent granular clinical concepts. The resources can be managed in isolation, or aggregated into complex documents. Technically, FHIR is designed for the web; the resources are based on simple XML or JSON structures, with an http-based RESTful protocol where each resource has predictable URL. Where possible, open internet standards are used for data representation.

FHIR is under active development by HL7 (Health Level Seven). Availability of translations in multiple languages would facilitate easier and faster adoption of FHIR and FHIR would bring tremendous benefits for health of more people all over the world.

Is HL7 FHIR Specification suitable to be added as a new project? If so, is it possible to load it without getting its established structure broken?

Please see below for details:

• The current specification: http://www.HL7.org/fhir/
• FHIR Overview: http://www.hl7.org/implement/standards/fhir/overview.html
• License and Legal Terms: http://www.hl7.org/implement/standards/fhir/license.html
• FHIR Wiki: http://wiki.hl7.org/index.php?title=FHIR
• FHIR SVN Trunk: http://gforge.hl7.org/svn/fhir/trunk
• hl7-fhir on GitHub: https://github.com/hl7-fhir
• Russian version (under translation): http://fhir-ru.github.io/index.html

So many thanks in advance!

Hello, we generally don't translate websites here, so it would be quite hard. As they have a MediaWiki wiki, the easiest would be that they install Translate to translate the specification there, and then find a way to "transclude" the translated HTML into their website.

Hi Nemo,

Thanks first!

The FHIR website is just an exact representation of the FHIR specification and it/its content is the same as the whole specification.

• A zipped official copy of the FHIR specification (i.e., the full site not including the downloads) can be downloaded from here.

Broadly, the FHIR specification is broken up into 3 parts (See here):

1. General documentation that describes how resources are defined, and gives background material including definitions of data types, codes, and the XML and JSON formats
2. Implementation - how to use resources using REST, Messaging, as clinical documents, or in a service based architecture
3. The resource list - a list of all the resources defined by FHIR. You can also get lists for clinical, administrative and infrastructural resources

The FHIR Wiki is a place where development processes, methodology and design decisions are documented.

• Implementers and others can also contribute to the wiki to provide additional guidance and supplemental information not found in the specification.
• Note that wiki content is not authoritative and is not relevant for determining conformance to the FHIR specification.
• As well, some wiki content may not be up to date with the most recent version of the FHIR specification.

Thanks agian.

Cheers,

This doesn't really change much.

1. We don't generally translate websites as we don't generally translate books, manuals or specifications.
2. The way the wiki is currently being used is not a divine order and is compatible with translation. Unless the specification "master" is already some structured [l10n] format, any translation system will require that the document is moved to the translation system/format and back. If the specs can be converted to YAML or JSON, they can as well be regularly sync'ed to wiki pages and translated there.

Hi Nemo,

Thanks for your replies :)

Cheers,

You're welcome. If you still conclude that translating here on translatewiki.net is better than using Translate on your wiki, let us know.

Thanks :) I will let you know if translatewiki.net is needed.