-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' into jr-20240325-concept-map-unmatched-codes
- Loading branch information
Showing
159 changed files
with
2,388 additions
and
920 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 changes: 6 additions & 0 deletions
6
.../src/main/resources/ca/uhn/hapi/fhir/changelog/7_2_0/5088-fix-history-bundle-fullUrl.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| --- | ||
| type: fix | ||
| issue: 5088 | ||
| title: "Previously, the fullUrl for resources in _history bundles was not generated correctly when using a client | ||
| provided id. The same problem started to happen for the resources with server generated ids more recently | ||
| (after 6.9.10). This has now been fixed" |
8 changes: 8 additions & 0 deletions
8
...resources/ca/uhn/hapi/fhir/changelog/7_2_0/5748-avoid-lob-usage-in-batch2-and-search.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| --- | ||
| type: perf | ||
| issue: 5748 | ||
| title: "In the JPA server, several database columns related to Batch2 jobs and searching | ||
| have been reworked so that they no will longer use LOB datatypes going forward. This | ||
| is a significant advantage on Postgresql databases as it removes a significant use | ||
| of the inefficient `pg_largeobject` table, and should yield performance boosts for | ||
| MSSQL as well." |
12 changes: 12 additions & 0 deletions
12
...r-docs/src/main/resources/ca/uhn/hapi/fhir/changelog/7_2_0/5750-update-cr-operations.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| --- | ||
| type: add | ||
| issue: 5750 | ||
| title: "Update to the 3.2.0 release of the Clinical Reasoning Module. This includes the following changes: | ||
| <ul> | ||
| <li>Updated the Clinical Reasoning documentation.</li> | ||
| <li>Added support for additional parameters on operations.</li> | ||
| <li>Added StructureDefinition/$questionnaire operation.</li> | ||
| <li>Add ability to generate PlanDefinition/$apply results with unique ids.</li> | ||
| <li>Resolved issues with Questionnaire item generation during PlanDefinition/$apply.</li> | ||
| <li>Resolved issues with some request resources not generated correctly from ActivityDefinition/$apply</li> | ||
| </ul>" |
6 changes: 6 additions & 0 deletions
6
...esources/ca/uhn/hapi/fhir/changelog/7_2_0/5800-enforce-maximum-bulk-export-file-size.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| --- | ||
| type: add | ||
| issue: 5800 | ||
| title: "A new setting in JpaStorageSettings enforces a maximum file size for Bulk Export | ||
| output files, as well as work chunks creating during processing. This setting has | ||
| a default value of 100 MB." |
5 changes: 5 additions & 0 deletions
5
...uhn/hapi/fhir/changelog/7_2_0/5802-fix-mdm-expansion-not-returning-expected-resources.yml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| type: fix | ||
| issue: 5802 | ||
| title: "Previously, using the ':mdm' qualifier with the '_id' search parameter would not included expanded resources in | ||
| search result. This issue has been fixed." |
48 changes: 48 additions & 0 deletions
48
...main/resources/ca/uhn/hapi/fhir/docs/clinical_reasoning/activity_definitions.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,48 @@ | ||
| # ActivityDefinition | ||
|
|
||
| ## Introduction | ||
|
|
||
| The FHIR Clinical Reasoning Module defines the [ActivityDefinition resource](https://www.hl7.org/fhir/activitydefinition.html) and several [associated operations](https://www.hl7.org/fhir/activitydefinition-operations.html). An ActivityDefinition is a shareable, consumable description of some activity to be performed. It may be used to specify actions to be taken as part of a workflow, order set, or protocol, or it may be used independently as part of a catalog of activities such as orderables. | ||
|
|
||
| In general, an activity definition is simply a conceptual description of some specific action that should be taken. An instance of an ActivityDefinition does not indicate that any action has been performed (as an event resource does), nor does it indicate the actual intent to carry out any particular action (as a request resource does). Instead, an activity definition provides a reusable template that can be used to construct specific request resources such as ServiceRequest and MedicationRequest. | ||
|
|
||
| Note that this is conceptually similar to the Task resource as well, with the distinction being that ActivityDefinition represents the description of a task in the abstract, while the Task resource is used to track a specific instance of a task as it moves through the steps of a workflow. | ||
|
|
||
| An ActivityDefinition resource provides a description, or template, of an action to perform. These actions can be purely text-based descriptions of the action to be performed, only interpretable by a human user, or they can be structured definitions with enough information to construct a resource to represent the request or activity directly. This process of converting the ActivityDefinition into a specific resource in a particular context is performed with the [$apply](/docs/clinical_reasoning/activity_definitions.html#apply) operation. | ||
|
|
||
| ## Operations | ||
|
|
||
| HAPI implements the following operations for ActivityDefinitions | ||
|
|
||
| * [$apply](/docs/clinical_reasoning/activity_definitions.html#apply) | ||
|
|
||
| ## Apply | ||
|
|
||
| The `ActivityDefinition/$apply` [operation](https://www.hl7.org/fhir/activitydefinition-operation-apply.html) creates a [Request Resource](https://www.hl7.org/fhir/workflow.html#request) for a given context. This implementation follows the [FHIR Specification](https://www.hl7.org/fhir/activitydefinition.html#12.22.4.3) and supports the [FHIR Clinical Guidelines IG](https://hl7.org/fhir/uv/cpg/index.html). | ||
|
|
||
| ### Parameters | ||
|
|
||
| The following parameters are supported for the `ActivityDefinition/$apply` operation: | ||
|
|
||
| | Parameter | Type | Description | | ||
| |---------------------|---------------------------|-------------| | ||
| | activityDefinition | ActivityDefinition | The activity definition to be applied. If the operation is invoked at the instance level, this parameter is not allowed; if the operation is invoked at the type level, this parameter is required, or a url (and optionally version) must be supplied. | | ||
| | canonical | canonical(ActivityDefinition) | The canonical url of the activity definition to be applied. If the operation is invoked at the instance level, this parameter is not allowed; if the operation is invoked at the type level, this parameter (and optionally the version), or the activityDefinition parameter must be supplied. | | ||
| | url | uri | Canonical URL of the ActivityDefinition when invoked at the resource type level. This is exclusive with the activityDefinition and canonical parameters. | | ||
| | version | string | Version of the ActivityDefinition when invoked at the resource type level. This is exclusive with the activityDefinition and canonical parameters. | | ||
| | subject | string(reference) | The subject(s) that is/are the target of the activity definition to be applied. | | ||
| | encounter | string(reference) | The encounter in context, if any. | | ||
| | practitioner | string(reference) | The practitioner applying the activity definition. | | ||
| | organization | string(reference) | The organization applying the activity definition. | | ||
| | userType | CodeableConcept | The type of user initiating the request, e.g. patient, healthcare provider, or specific type of healthcare provider (physician, nurse, etc.) | | ||
| | userLanguage | CodeableConcept | Preferred language of the person using the system | | ||
| | userTaskContext | CodeableConcept | The task the system user is performing, e.g. laboratory results review, medication list review, etc. This information can be used to tailor decision support outputs, such as recommended information resources. | | ||
| | setting | CodeableConcept | The current setting of the request (inpatient, outpatient, etc.). | | ||
| | settingContext | CodeableConcept | Additional detail about the setting of the request, if any | | ||
| | parameters | Parameters | Any input parameters defined in libraries referenced by the ActivityDefinition. | | ||
| | useServerData | boolean | Whether to use data from the server performing the evaluation. If this parameter is true (the default), then the operation will use data first from any bundles provided as parameters (through the data and prefetch parameters), second data from the server performing the operation, and third, data from the dataEndpoint parameter (if provided). If this parameter is false, the operation will use data first from the bundles provided in the data or prefetch parameters, and second from the dataEndpoint parameter (if provided). | | ||
| | data | Bundle | Data to be made available to the ActivityDefinition evaluation. | | ||
| | dataEndpoint | Endpoint | An endpoint to use to access data referenced by retrieve operations in libraries referenced by the ActivityDefinition. | | ||
| | contentEndpoint | Endpoint | An endpoint to use to access content (i.e. libraries) referenced by the ActivityDefinition. | | ||
| | terminologyEndpoint | Endpoint | An endpoint to use to access terminology (i.e. valuesets, codesystems, and membership testing) referenced by the ActivityDefinition. | | ||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.