|
Type
|
Reference
|
Content
|
|
web
|
github.com
|
FHIR Terminology Ecosystem IG, published by HL7 FHIR Product Director. This guide is not an authorized publication; it is the continuous build for version 1.11.1-snapshot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-tx-ecosystem-ig/
and changes regularly. See the Directory of published versions
|
|
web
|
keepachangelog.com
|
All notable changes to this IG will be documented in this file. The format is based on Keep a Changelog
.
|
|
web
|
github.com
|
The IG now separates the ecosystem framework from HL7's own instance of it: other authorities and networks can run their own ecosystems with the same framework. The registration process for HL7's ecosystem is documented in the ig-registry
, and the coordination server has its own page
|
|
web
|
github.com
|
Approval is about the server
- the implementation, and the public endpoint that demonstrates it. It
is a different thing from being registered
in the ecosystem, which is about a particular deployment
being authoritative
for particular content, and is recorded in
the server registries
rather than here. In HL7's own ecosystem, a
server has to be approved before a deployment of it is registered (see
the HL7 ecosystem documentation
),
but an approved server may have no registered deployments, and one approved server may have many. Other
ecosystems may have different registration policies and processes.
|
|
web
|
github.com
|
FHIRsmith
|
|
web
|
www.healthintersections.com.au
|
Health Intersections Pty Ltd
|
|
web
|
ontoserver.app
|
Ontoserver
|
|
web
|
aehrc.csiro.au
|
CSIRO Australian e-Health Research Centre
|
|
web
|
docs.helex.org
|
HELEX Terminology Aggregator
|
|
web
|
helex-solutions.com
|
HELEX Solutions
|
|
web
|
docs.helex.org
|
HELEX Terminology Server
|
|
web
|
www.healthall.co.kr
|
HealthAll
|
|
web
|
github.com
|
An existing entry
is maintained by the server's provider. Providers keep their own row current -
particularly the test cases version and the modes, both of which move as the server is released - by
raising a pull request against input/pagecontent/approved-servers.md
in the
IG's repository
. A provider does not need to ask before
correcting their own row.
|
|
web
|
github.com
|
HL7 manages one ecosystem, the public one used by the FHIR tools; its locations and registration process
are documented at https://github.com/FHIR/ig-registry/blob/master/tx-registry-doco.md
.
|
|
web
|
icd.who.int
|
ICD-11 is licensed by WHO under the Creative Commons Attribution-NoDerivs 3.0 IGO license
(CC BY-ND 3.0 IGO); see the ICD-11 license
and the
full ICD-11 Terms of Use and License Agreement
.
|
|
web
|
icd.who.int
|
ICD-11 is licensed by WHO under the Creative Commons Attribution-NoDerivs 3.0 IGO license
(CC BY-ND 3.0 IGO); see the ICD-11 license
and the
full ICD-11 Terms of Use and License Agreement
.
|
|
web
|
icdcdn.who.int
|
See the ICD-11 Reference Guide,
Extension codes and postcoordination
and
Adding detail - postcoordination and cluster coding
,
for WHO's account of postcoordination and cluster coding.
|
|
web
|
icdcdn.who.int
|
See the ICD-11 Reference Guide,
Extension codes and postcoordination
and
Adding detail - postcoordination and cluster coding
,
for WHO's account of postcoordination and cluster coding.
|
|
web
|
icd.who.int
|
ICF is published by WHO, and the same rules apply to licensing ICF as to licensing ICD. See
http://icd.who.int/
and
WHO's ICF pages
.
|
|
web
|
www.who.int
|
ICF is published by WHO, and the same rules apply to licensing ICF as to licensing ICD. See
http://icd.who.int/
and
WHO's ICF pages
.
|
|
web
|
icd.who.int
|
The ICD-11 test cases are jointly maintained by WHO
and the HL7 community, and are authoritative for ICD-11. The WHO FHIR API implementation conforms to these tests, as must other recognized ICD-11 servers
|
|
web
|
github.com
|
A server becomes an Approved Server
by passing the test cases for the
modes it claims, against a released version, on a public test endpoint, and being approved by the
FHIR Product Director. Problems with the test cases, or with the requirements,
are firstly discussed on the Terminology Service Test Cases at chat.fhir.org
,
and then can be raised as issues or PRs on the IG's repository
. Changes to the tests
are worked through with the authors of the servers, and agreed with the FHIR Product Director.
|
|
web
|
github.com
|
This specification is maintained by Grahame Grieve, as FHIR Product Director, and Reuben Daniels, as Deputy FHIR
Product Director. Contributions are made under the HL7 GOM
, and
the IG is built with the standard HL7 ci-build for IGs, which checks the generated QA. The license is in the
repository
. The content is used by, and built into, the base FHIR tools, which use the ecosystem for every version of FHIR after R4.
|
|
web
|
docs.github.com
|
This IG contains no active content. If you think there is a security issue in the terminology ecosystem
as it is documented here, report it privately using GitHub's
security reporting
on the IG's repository
, or email the
FHIR Product Director
. A security issue with one of the servers in the
ecosystem should be reported to that server's operators.
|
|
web
|
github.com
|
This IG contains no active content. If you think there is a security issue in the terminology ecosystem
as it is documented here, report it privately using GitHub's
security reporting
on the IG's repository
, or email the
FHIR Product Director
. A security issue with one of the servers in the
ecosystem should be reported to that server's operators.
|
|
web
|
github.com
|
The tests can be run by any runner that processes the tests correctly, but the easiest way to
execute the tests is to use the standard Java FHIR Validator
.
You do not download the tests yourself - the runner fetches the published test package for you:
|