You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: en/docs/configurations/email-notification.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ This is a required configuration.
43
43
<strong>Note:</strong>The values given within '${}' are the default placeholders that will be populated internally.
44
44
45
45
:::
46
-
### Upon User Approval/Rejection - To Specified Roles and Receipients
46
+
### Upon User Approval/Rejection - To Specified Roles and Recipients
47
47
48
48
```json
49
49
[[healthcare.notification.mail]]
@@ -77,7 +77,7 @@ This is a required configuration.
77
77
email_body = "<html><body>A new application has been created. Visit the <a href=\"${server_url}/admin/tasks/application-creation/\">admin portal</a> to approve/reject.</body></html>"
78
78
```
79
79
80
-
### Upon Application Approval/Rejection - To Specified Roles and Receipients
80
+
### Upon Application Approval/Rejection - To Specified Roles and Recipients
Copy file name to clipboardExpand all lines: en/docs/data-transformation/guides/hl7v2-fhir.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -220,11 +220,11 @@ The service processes incoming POST requests containing HL7v2 messages. When a m
220
220
221
221
Let's look into the the detailed implementation of this. Let's assume the [custom-service-openapi.yaml](../references/custom-service-openapi.yaml) is inside the resources folder.
222
222
223
-
1.Genarate the files using openapi files as below.
223
+
1.Generate the files using openapi files as below.
224
224
```bash
225
225
bal openapi -i resources/custom-service-openapi.yaml --mode service -o <OUTPUT-FOLDER>
226
226
```
227
-
2.They types.bal file is auto generated to the specified folder and it does not need any changes to be done.
227
+
2.The types.bal file is auto generated to the specified folder and it does not need any changes to be done.
228
228
3. Update the custom-service-openapi-service.bal file as below.
Copy file name to clipboardExpand all lines: en/docs/fhir/guides/connecting-ehr-emr-systems.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,12 @@ title: "Connecting Ehr EMR Systems"
4
4
description: WSO2’s solution offers out-of-the-box connectors for Health Care vendors such as EPIC, Cerner, and Athena Health EMRs and is capable of generating connectors automatically to any F.
5
5
---
6
6
7
-
#Connecting EHR/EMR Systems
7
+
#Connecting EHR/EMR Systems
8
8
9
-
##Overview
10
-
WSO2’s solution offers out-of-the-box connectors for Health Care vendors such as EPIC, Cerner, and Athena Health EMRs and is capable of generating connectors automatically to any FHIRbased or Open API specificationbased EHR/EMR system.<br /> These connectors will increase the developer's productivity by providing an abstraction to the EHR/EMR system endpoints, but are not a must for WSO2 to integrate with an EHR/EMR.<br /><br /> This section will provide instruction on how to obtain the EHR/EMR connectors, how to install them, and how to use them.
9
+
##Overview
10
+
WSO2’s solution offers out-of-the-box connectors for Health Care vendors such as EPIC, Cerner, and Athena Health EMRs and is capable of generating connectors automatically to any FHIR-based or Open API specification-based EHR/EMR system.<br /> These connectors will increase the developer's productivity by providing an abstraction to the EHR/EMR system endpoints, but are not a must for WSO2 to integrate with an EHR/EMR.<br /><br /> This section will provide instruction on how to obtain the EHR/EMR connectors, how to install them, and how to use them.
11
11
12
-
##Set up the required connectors
12
+
##Set up the required connectors
13
13
Follow the instructions given below to set up the connectors you require in your WSO2 Integration Studio.
14
14
<ul>
15
15
<li> You can request a connector for any FHIR compliant EHR/EMR system, or a system that has an Open API specification.</li>
@@ -18,10 +18,10 @@ Follow the instructions given below to set up the connectors you require in your
18
18
<li> The connector zip file will be provided after it is generated by the tool.</li>
19
19
</ul>
20
20
21
-
##Install the connector
21
+
##Install the connector
22
22
As mentioned in the previous section, WSO2 Integration Studio is the IDE that will be used to develop integrations that will be deployed in the integration layer of the Healthcare solution. The connector zip that is obtained from WSO2 should be imported to the Integration Studio in order to develop the integration flow.<br /> Steps on installing and using the connector can be found by clicking the [link](https://apim.docs.wso2.com/en/4.0.0/reference/connectors/connectors-overview/#how-to-use-connectors)<br />
23
23
24
-
##Connect system to integration logic
24
+
##Connect system to integration logic
25
25
In this section let’s walk through a simple example of connecting to the Epic EHR system and searching and retrieving some patient data. Epic is a FHIR compliant EHR system. WSO2 has a pre-built connector for the Epic sandbox environment. Let’s create a new Integration project and add a Rest API to it. More information on creating the integration project,and the Rest API can be found [here](https://apim.docs.wso2.com/en/4.0.0/integrate/develop/integration-development-kickstart/).<br />Then let's import the Epic connector to the Integration Studio as mentioned in the previous section. Once imported the mediator <strong>Palette</strong> of the Integration Studio will have the Epic connector listed. As shown in the below image:
26
26
27
27
@@ -30,7 +30,7 @@ The required connector operations have to be dragged and dropped to the canvas.
30
30
31
31
32
32
33
-
The above image describes the user of the init and the searchPatient connector operations. When an operation is clicked the following property pane will be visible with all the parameters that the operation would accept.
33
+
The above image describes the use of the init and the searchPatient connector operations. When an operation is clicked the following property pane will be visible with all the parameters that the operation would accept.
Copy file name to clipboardExpand all lines: en/docs/fhir/guides/expose-fhir-apis.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,10 +55,10 @@ Please note that there are areas that WSO2 Open Healthcare does not support at t
55
55
56
56
Once the required FHIR resources have been exposed as FHIR APIs, the server is ready to go as a standard FHIR server. That is, all the subordinate components are getting updated and deployed accordingly.
57
57
58
-
To learn more about RESTful FHIR, refer the [official FHIR documentation](https://www.hl7.org/fhir/http.html).
58
+
To learn more about RESTful FHIR, refer to the [official FHIR documentation](https://www.hl7.org/fhir/http.html).
59
59
60
60
- Interactions
61
-
- Instance level - All the instance level interactions are pre templeted in the API definitions of the WSO2 FHIR API Hub. Relevant backend integration logic has to be implemented by the developer. (A project skeleton with boilerplate code will be provided to speed up the deployment.)
61
+
- Instance level - All the instance level interactions are pre-templated in the API definitions of the WSO2 FHIR API Hub. Relevant backend integration logic has to be implemented by the developer. (A project skeleton with boilerplate code will be provided to speed up the deployment.)
62
62
- Type level - Type level interactions are also handled in a similar manner as in Instance level interactions.
63
63
- System level - Only Capabilities interaction is available as a default feature.
64
64
- Capability statement
@@ -80,7 +80,7 @@ To learn more about RESTful FHIR, refer the [official FHIR documentation](https:
| read | yes | Supports query parameters as well |
83
-
| vread | yes | Appropriate Integration logic has to be implemented by the Integration developer. (Since versioning strategy might different from one system to a another) |
83
+
| vread | yes | Appropriate Integration logic has to be implemented by the Integration developer. (Since versioning strategy might differ from one system to another) |
84
84
| update | yes | Appropriate Integration logic has to be implemented by the Integration developer. |
85
85
| patch | yes | Appropriate Integration logic has to be implemented by the Integration developer. |
This method will allow the user to create a new current version for an existing resource by updating part of the resource.For we only support [FHIRPath Patch](https://hl7.org/FHIR/fhirpatch.html), the remaining content types will be supported in the future releases.
131
+
This method will allow the user to create a new current version for an existing resource by updating part of the resource. Currently only [FHIRPath Patch](https://hl7.org/FHIR/fhirpatch.html) is supported; the remaining content types will be supported in future releases.
| | *returnMimeType* - The [Mime Type](https://www.hl7.org/fhir/http.html#mime-type:~:text=Content%20Types%20and%20encodings) of the return response |
174
174
| | uriParameters - additional [params](https://www.hl7.org/fhir/http.html#history:~:text=_format%20parameter%2C%20the-,parameters,-to%20this%20interaction) as a name value map |
This method will allow the user to create a new for a specified type. Here the user doesn't have control over the resource ID, it will be assigned by the server.
187
+
This method will allow the user to create a new resource for a specified type. Here the user doesn't have control over the resource ID, it will be assigned by the server.
| `implementationUrl` | Base URL for the installation <br/><br/> eg: `https://choreoapis/dev/fhir_server/0.1.5` |
96
96
| `implementationDescription` | Describes this specific instance <br/><br/> eg: `WSO2 Open Healthcare FHIR` |
97
-
| `interaction` | The that operations are supported <br/><br/> eg: `[search-system, history-system]` |
97
+
| `interaction` | The operations that are supported <br/><br/> eg: `[search-system, history-system]` |
98
98
| `cors` | CORS Headers availability <br/><br/> eg: `true` |
99
99
| `discoveryEndpoint` | The discovery endpoint for the server <br/><br/> eg: `https://api.asgardeo.io/t/<organization_name>/oauth2/token/.well-known/openid-configuration` |
100
100
| `tokenEndpoint` | OPTIONAL: If not provided a discoveryEndpoint. <br/>OAUTH2 access token url <br/><br/> eg: `https://api.asgardeo.io/t/<organization_name>/oauth2/token` |
101
101
| `revocationEndpoint` | OPTIONAL: If not provided a discoveryEndpoint. <br/>OAUTH2 access revoke url <br/><br/> eg: `https://api.asgardeo.io/t/<organization_name>/oauth2/revoke` |
102
102
| `authorizeEndpoint` | OPTIONAL: If not provided a discoveryEndpoint. <br/>OAUTH2 access authorize url <br/><br/> eg: `https://api.asgardeo.io/t/<organization_name>/oauth2/authorize` |
103
103
104
-
A sample `Config.toml` is consisting above configurations as below.
104
+
A sample `Config.toml` containing the above configurations is shown below.
105
105
106
106
```
107
107
## server related configurables
@@ -222,7 +222,7 @@ This creates the organization and opens the Project Home page of the default pro
222
222
223
223
Follow the official documentation to deploy the smart configuration prebuilt service to your organization https://wso2.com/choreo/docs/develop-components/develop-services/develop-a-ballerina-rest-api/#step-2-build-and-deploy.
224
224
225
-
On deployment configurables mentioned in [Configurations](#configurations) needs to be configured in Choreo configurable editor.
225
+
On deployment, configurables mentioned in [Configurations](#configurations) need to be configured in the Choreo configurable editor.
226
226
227
227
## Configurations
228
228
@@ -246,7 +246,7 @@ Following configurations need to be added in a `Config.toml` or in the Choreo co
246
246
| `capabilities` | REQUIRED, Array of strings representing SMART capabilities (e.g., sso-openid-connect or launch-standalone) that the server supports. <br/><br/> eg: `[launch-ehr, permission-patient, permission-v2, client-public, client-confidential-symmetric, context-ehr-patient, sso-openid-connect, launch-standalone, context-standalone-patient, permission-offline]` |
247
247
| `codeChallengeMethodsSupported` | REQUIRED, Array of PKCE code challenge methods supported. The S256 method SHALL be included in this list, and the plain method SHALL NOT be included in this list. <br/><br/> eg: `[S256]`
248
248
249
-
A sample `Config.toml` is consisting above configurations as below.
249
+
A sample `Config.toml` containing the above configurations is shown below.
Copy file name to clipboardExpand all lines: en/docs/fhir/guides/parsing-and-serializing.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ Before you begin, ensure you have <a href="https://ballerina.io/downloads/instal
26
26
```bash
27
27
$ bal new fhir_parsing_sample
28
28
```
29
-
2. Import the required modules to the Ballerina program. In this sample we are using FHIR Patient resource from international base FHIR IG. Therefore, we need to import `ballerinax/health.fhir.r4.internationa401` package. If you are using a different IG of FHIR, you can import the relevant package from the [central](https://central.ballerina.io/search?q=fhir&page=1&m=packages) or generated from the bal [health tool](https://ballerina.io/learn/health-tool/#package-generation).
29
+
2. Import the required modules to the Ballerina program. In this sample we are using FHIR Patient resource from international base FHIR IG. Therefore, we need to import `ballerinax/health.fhir.r4.international401` package. If you are using a different IG of FHIR, you can import the relevant package from the [central](https://central.ballerina.io/search?q=fhir&page=1&m=packages) or generated from the bal [health tool](https://ballerina.io/learn/health-tool/#package-generation).
0 commit comments