Skip to content

CTHLU-12 - remove xml hl7 parser service #75

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
adaball wants to merge 4 commits into
base: main
Choose a base branch
from
Draft

CTHLU-12 - remove xml hl7 parser service #75

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5e5f49b
Remove 9c_xml_hl7_parser.md
Apr 7, 2026
f711124
Remove xml hl7 parser from keycloak
Apr 7, 2026
6fee831
Add `.idea` to .gitignore
Apr 7, 2026
4cbf8d7
Remove XML HL7 Parser Service from microservices deployment section
Apr 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,3 +15,6 @@ _site/
vendor/
.DS_Store
node_modules/

# IntelliJ
.idea/
9 changes: 0 additions & 9 deletions docs/5_keycloak/1_keycloak_installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,12 +161,3 @@ The imported configuration seeds a random client secret for each service client.
1. Select `srte-data-keycloak-client` and open the **Credentials** tab.
1. Click the eye icon to reveal the secret and copy it.
1. Store the secret (for example, in AWS Secrets Manager at `keycloak/client/secret/srte`).

### XML-HL7 parser client

1. In the **NBS Realm**, open **Realm settings**, click the **Action** dropdown, and select **Partial Import**.
1. Upload `<Helm extract directory>/charts/keycloak/extra/10-nbs-users-xml-hl7-parser-service.json` and click **Create**.
1. Navigate to the **NBS Realm** in the left menu and click **Clients**.
1. Select `xml-hl7-parser-keycloak-client` and open the **Credentials** tab.
1. Click the eye icon to reveal the secret and copy it.
1. Store the secret (for example, in AWS Secrets Manager at `keycloak/client/secret/xml-hl7-parser`).
2 changes: 0 additions & 2 deletions docs/6_microservices_deployment/9_case_notification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,6 @@ nav_enabled: true
- If STLT choose modernize, then we can proceed with the following steps
- If choose NOT to deploy Case Notification Service, these following services should not be turned on in Kubernetes
- Debezium Case Notification
- XML HL7 Parser Service
- Data Extraction Service
- Case Notification Service

Expand All @@ -37,6 +36,5 @@ This guide sets out the detailed steps to installing NBS 7 Case Notification, en

- Case Notification consist of 4 services and should be deployed in this top down order
- Debezium Case Notification
- XML HL7 Parser Service
- Data Extraction Service
- Notification Service
1 change: 0 additions & 1 deletion docs/6_microservices_deployment/9b_keycloak_configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,4 +24,3 @@ nav_enabled: true

2. The 3 Case notification service except for Debezium will also need keycloak profile
[NEDSS-Helm/charts/keycloak/extra at main · CDCgov/NEDSS-Helm](https://github.com/CDCgov/NEDSS-Helm/tree/main/charts/keycloak/extra)
3. Note: in Case-Notification-Service, it require XML-HL7-Parser-service keycloak id and secret to be definied in the environment variable
58 changes: 0 additions & 58 deletions docs/6_microservices_deployment/9c_xml_hl7_parser.md
View file
Open in desktop

This file was deleted.

5 changes: 0 additions & 5 deletions docs/6_microservices_deployment/9e_case_notification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,11 +40,6 @@ nav_enabled: true

kafka:
cluster: "EXAMPLE_MSK_KAFKA_ENDPOINT"

api:
host: "https://<data.EXAMPLE_DOMAIN>/hl7-parser"
clientId: "EXAMPLE_XML-HL7-Parser_CLIENT_ID"
secret: "EXAMPLE_XML-HL7-Parser_CLIENT_SECRET"
```

4. Install Pod
Expand Down
4 changes: 0 additions & 4 deletions docs/6_microservices_deployment/9f_testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,10 +74,6 @@ nav_enabled: true
- a. [NEDSS-NNDSS-Case-Notifications/README.md at main · CDCgov/NEDSS-NNDSS-Case-Notifications](https://github.com/CDCgov/NEDSS-NNDSS-Case-Notifications/blob/main/README.md)
- b. [NEDSS-Helm/charts/data-extraction-service/templates/deployment.yaml at main · CDCgov/NEDSS-Helm](https://github.com/CDCgov/NEDSS-Helm/blob/main/charts/data-extraction-service/templates/deployment.yaml)

3. **Xml-Hl7-Parser-Service**
- a. [NEDSS-NNDSS-Case-Notifications/README.md at main · CDCgov/NEDSS-NNDSS-Case-Notifications](https://github.com/CDCgov/NEDSS-NNDSS-Case-Notifications/blob/main/README.md)
- b. [NEDSS-Helm/charts/xml-hl7-parser-service/templates/deployment.yaml at main · CDCgov/NEDSS-Helm](https://github.com/CDCgov/NEDSS-Helm/blob/main/charts/xml-hl7-parser-service/templates/deployment.yaml)

---

#### Case Notification Liquibase
Expand Down