honeymoose
/
hapi-fhir
mirror of https://github.com/hapifhir/hapi-fhir.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2116 from jamesagnew/im_2020_09_29_term_doc_updates 

Im 2020 09 29 term doc updates
This commit is contained in:
IanMMarshall 2020-10-05 16:24:17 -04:00 committed by GitHub
parent f1710fd0be 5ec1284b8a
commit ce54d28a23
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
7 changed files with 297 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/5_2_0/2081-multiple-version-code-systems.yaml
View File

@ -1,4 +1,4 @@
--- ---
type: add type: add
issue: 2081 issue: 2081
title: "Operations for CodeSystem, ValueSet and ConcepMap will now support multiple CodeSystem versions." title: "Operations for CodeSystem, ValueSet and ConceptMap will now support multiple CodeSystem versions."

1
hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/files.properties
View File

@ -49,6 +49,7 @@ page.server_jpa.performance=Performance
page.server_jpa.upgrading=Upgrade Guide page.server_jpa.upgrading=Upgrade Guide
page.server_jpa.diff=Diff Operation page.server_jpa.diff=Diff Operation
page.server_jpa.lastn=LastN Operation page.server_jpa.lastn=LastN Operation
page.server_jpa.terminology=Terminology
section.server_jpa_empi.title=JPA Server: EMPI section.server_jpa_empi.title=JPA Server: EMPI
page.server_jpa_empi.empi=EMPI Getting Started page.server_jpa_empi.empi=EMPI Getting Started

1
hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/images/termcodesystem_schema.svg Normal file
View File

File diff suppressed because one or more lines are too long
Side by Side

After

Width:  |  Height:  |  Size: 70 KiB

1
hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/images/termconceptmap_schema.svg Normal file
View File

File diff suppressed because one or more lines are too long
Side by Side

After

Width:  |  Height:  |  Size: 59 KiB

1
hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/images/termvalueset_schema.svg Normal file
View File

File diff suppressed because one or more lines are too long
Side by Side

After

Width:  |  Height:  |  Size: 45 KiB

286
hapi-fhir-docs/src/main/resources/ca/uhn/hapi/fhir/docs/server_jpa/terminology.md Normal file
View File

@ -0,0 +1,286 @@
# Terminology
HAPI FHIR JPA Server includes an `IValidationSupport` class, `JpaPersistedResourceValidationSupport`, which can be used to validate terminology using CodeSystem, ValueSet and ConceptMap resources provided by the JPA Server. Terminology can be loaded into the JPA Server using standard FHIR REST APIs (PUT and POST) as well as using the hapi-fhir-cli [upload-terminology](/hapi-fhir/docs/tools/hapi_fhir_cli.html#upload-terminology) command.
# Versioning of Terminology
Code systems can be versioned as described in the FHIR specification [here](http://hl7.org/fhir/codesystem.html#versioning). Similarly, value sets and concept maps that are defined with a versioned code system can also be versioned.
Versions of a given code system, value set or concept map are differentiated from each other by the CodeSystem.version, ValueSet.version and ConceptMap.version properties respectively. Each version of a given code system, value set and concept map will have a separate resource entity. This version should not be confused with the resource version (i.e. Resource.meta.versionId).
When queries or operations are requested with a specific CodeSystem, ValueSet, or ConceptMap url and version specified, the JPA Server will act on the resource(s) specified by or linked to the version. If the same request is submitted with no version specified, the JPA Server will instead act on the current (i.e. most recently updated) version of the resource identified by the URL.
Delta Add and Remove modes in the [upload-terminology](/hapi-fhir/docs/tools/hapi_fhir_cli.html#upload-terminology) command will only be applied to the most recently updated version.
# Terminology Schemas
This page provides the schema of tables that are used to complement the CodeSystem, ValueSet and ConceptMap resources, and which map the relationships between these resources and various properties that are used or referenced by terminology operations.
## CodeSystem Tables
<img src="/hapi-fhir/docs/images/termcodesystem_schema.svg" alt="Resources" style="width: 100%; max-width: 600px;"/>
The TRM_CODESYSTEM_VER table represents a single CodeSystem resource with a specific URL and version. It is used to map terminology concepts represented by various TRM_CONCEPT_* tables to a single CodeSystem resource.
The TRM_CODESYSTEM table represents the canonical representation of a CodeSystem resource with a specific URL and maps to a single TRM_CODESYSTEM_VER row which is treated as the current version of the CodeSystem (i.e. the resource referenced if no version is specified). For example, two CodeSystem resources `CodeSystem/loinc-2.67` and `CodeSystem/loinc-2.68` might have the same CodeSystem.url, e.g. `http://loinc.org` but different CodeSystem.version values. In this case each will each have exactly one row in the TRM_CODESYSTEM_VER table, but there will be only one row in the TRM_CODESYSTEM table which will link only to the more recently updated TRM_CODESYSTEM_VER resource.
### Columns
The following are the main key columns in the TRM_CODESYSTEM_VER table that are used to join to the TRM_CODESYSTEM table and TRM_CONCEPT_* tables.
<table class="table table-striped table-condensed">
<thead>
<tr>
<th>Name</th>
<th>Relationships</th>
<th>Datatype</th>
<th>Nullable</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>PID</td>
<td></td>
<td>Long</td>
<td></td>
<td>
Persistent ID of the TRM_CODESYSTEM_VER row.
</td>
</tr>
<tr>
<td>RES_ID</td>
<td></td>
<td>Long</td>
<td></td>
<td>
Persistent ID of the CodeSystem resource in the HFJ_RESOURCE table.
</td>
</tr>
<tr>
<td>CODESYSTEM_PID</td>
<td></td>
<td>Long</td>
<td>Nullable</td>
<td>
Persistent ID of the TRM_CODESYSTEM row for the canonical representation of this CodeSystem resource.
</td>
</tr>
<tr>
<td>CS_VERSION_ID</td>
<td></td>
<td>Long</td>
<td>Nullable</td>
<td>
CodeSystem.version of the CodeSystem resource.
</td>
</tr>
</tbody>
</table>
The TRM_CODESYSTEM_VER table will have exactly one row for each unique combination of CODESYSTEM_PID and CS_VERSION_ID.
The following are the main key columns in the TRM_CODESYSTEM table.
<table class="table table-striped table-condensed">
<thead>
<tr>
<th>Name</th>
<th>Relationships</th>
<th>Datatype</th>
<th>Nullable</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>PID</td>
<td></td>
<td>Long</td>
<td></td>
<td>
Persistent ID of the TRM_CODESYSTEM row.
</td>
</tr>
<tr>
<td>CODE_SYSTEM_URI</td>
<td></td>
<td>String</td>
<td></td>
<td>
URL of the CodeSystem resource.
</td>
</tr>
<tr>
<td>CURRENT_VERSION_PID</td>
<td></td>
<td>Long</td>
<td>Nullable</td>
<td>
Persistent ID of the TRM_CODESYSTEM_VER row for the most recently updated version of the CodeSystem resource for this URL.
</td>
</tr>
<tr>
<td>CS_NAME</td>
<td></td>
<td>String</td>
<td>Nullable</td>
<td>
CodeSystem.name value for this CodeSystem resource.
</td>
</tr>
<tr>
<td>RES_ID</td>
<td></td>
<td>Long</td>
<td>Nullable</td>
<td>
Persistent ID of the most recently updated version of the CodeSystem resource for this URL in the HFJ_RESOURCE table.
</td>
</tr>
</tbody>
</table>
The TRM_CODESYSTEM table will have exactly one row for each unique CODE_SYSTEM_URI value.
## ValueSet Tables
<img src="/hapi-fhir/docs/images/termvalueset_schema.svg" alt="Resources" style="width: 100%; max-width: 600px;"/>
The TRM_VALUESET table represents a single ValueSet resource with a specific URL and version. It can be used to map terminology concepts represented by the TRM_VALUESET_CONCEPT and TRM_VALUESET_C_DESIGNATION tables to a single ValueSet resource.
### Columns
The following are the main key columns in the TRM_VALUESET table that are used to join to the TRM_VALUESET_CONCEPT and TRM_VALUESET_C_DESIGNATION tables.
<table class="table table-striped table-condensed">
<thead>
<tr>
<th>Name</th>
<th>Relationships</th>
<th>Datatype</th>
<th>Nullable</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>PID</td>
<td></td>
<td>Long</td>
<td></td>
<td>
Persistent ID of the TRM_VALUESET row.
</td>
</tr>
<tr>
<td>RES_ID</td>
<td></td>
<td>Long</td>
<td>Nullable</td>
<td>
Persistent ID of the ValueSet resource in the HFJ_RESOURCE table.
</td>
</tr>
<tr>
<td>URL</td>
<td></td>
<td>String</td>
<td></td>
<td>
Canonical URL for the ValueSet resource.
</td>
</tr>
<tr>
<td>VER</td>
<td></td>
<td>String</td>
<td>Nullable</td>
<td>
ValueSet.version for this ValueSet resource.
</td>
</tr>
</tbody>
</table>
The TRM_VALUESET table will have exactly one row for each unique combination of URL and VER.
## ConceptMap Tables
<img src="/hapi-fhir/docs/images/termconceptmap_schema.svg" alt="Resources" style="width: 100%; max-width: 600px;"/>
The TRM_CONCEPTMAP table represents a single ConceptMap resource with a specific URL and version. It can be used to map terminology concepts to one another in groups.
### Columns
The following are the main key columns in the TRM_CONCEPTMAP table that are used to join to the TRM_CONCEPTMAP_* tables.
<table class="table table-striped table-condensed">
<thead>
<tr>
<th>Name</th>
<th>Relationships</th>
<th>Datatype</th>
<th>Nullable</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>PID</td>
<td></td>
<td>Long</td>
<td></td>
<td>
Persistent ID of the TRM_CONCEPTMAP row.
</td>
</tr>
<tr>
<td>RES_ID</td>
<td></td>
<td>Long</td>
<td>Nullable</td>
<td>
Persistent ID of the ConceptMap resource in the HFJ_RESOURCE table.
</td>
</tr>
<tr>
<td>SOURCE_URL</td>
<td></td>
<td>String</td>
<td>Nullable</td>
<td>
URL of the source ValueSet to be mapped.
</td>
</tr>
<tr>
<td>TARGET_URL</td>
<td></td>
<td>String</td>
<td>Nullable</td>
<td>
URL of the target ValueSet to be mapped.
</td>
</tr>
<tr>
<td>URL</td>
<td></td>
<td>String</td>
<td></td>
<td>
Canonical URL for the ConceptMap resource.
</td>
</tr>
<tr>
<td>VER</td>
<td></td>
<td>String</td>
<td>Nullable</td>
<td>
ConceptMap.version for this ConceptMap resource.
</td>
</tr>
</tbody>
</table>
The TRM_CONCEPTMAP table will have exactly one row for each unique combination of URL and VER.

6
hapi-fhir-jpaserver-base/src/main/resources/ca/uhn/fhir/jpa/term/loinc/loincupload.properties
View File

@ -73,6 +73,12 @@ loinc.answerlist.version=Beta.1
## Key may be omitted ## Key may be omitted
loinc.conceptmap.version=Beta.1 loinc.conceptmap.version=Beta.1
# This is the version for an uploaded code system (i.e. `CodeSystem.version`).
# If specified, a versioned instance of the CodeSystem will be loaded and this version value will be appended to the terminology resource ID values
# to distinguish these resources from other versioned instances (i.e. CodeSystem.id, ValueSet.id, and ConceptMap.id).
## Key may be omitted
#loinc.codesystem.version=2.68
# Group # Group
## Default value if key not provided: AccessoryFiles/GroupFile/Group.csv ## Default value if key not provided: AccessoryFiles/GroupFile/Group.csv
## File may be omitted ## File may be omitted