Environment Configurations
PACS DB Configurations
Variable Name | Description |
---|---|
PACS_DB_HOST | The host name of the postgres server which runs database for dcm4chee and pacs-integration |
PACS_DB_PORT | The port of the postgres server for dcm4chee and pacs-integration |
PACS_DB_ROOT_PASSWORD | The root password given to the postgres container ie pacsdb service |
DCM4CHEE Configurations
Variable Name | Description |
---|---|
DCM4CHEE_IMAGE_TAG | This value specifies which image version needs to be used for dcm4chee service. List of tags can be found at bahmni/dcm4chee - Tags . |
DCM4CHEE_DB_NAME | The name of the database for dcm4chee service |
DCM4CHEE_DB_USERNAME | Username for connecting to dcm4chee database |
DCM4CHEE_DB_PASSWORD | Password for connecting to dcm4chee database |
PACS-Integration Configurations
Variable Name | Description |
---|---|
PACS_INTEGRATION_IMAGE_TAG | This value specifies which image version needs to be used for pacs-integration service. List of tags can be found at bahmni/pacs-integration - Tags . |
PACS_INTEGRATION_DB_NAME | The name of the database for pacs-integration service |
PACS_INTEGRATION_DB_USERNAME | Username for connecting to pacs-integration database |
PACS_INTEGRATION_DB_PASSWORD | Password for connecting to pacs-integration database |
PACS Simulator Configurations
Should be used for testing / demo environments. In a production setup this would be replaced by actual Modality machine (Example: X-Ray Machine)
Variable Name | Description |
---|---|
PACS_SIMULATOR_IMAGE_TAG | This value specifies which image version needs to be used for pacs-simulator service. List of tags can be found at bahmni/pacs-simulator - Tags . |
PACS_SIMULATOR_TIMEOUT | The timeout value for PACS Simulator while sending DICOM Image to the given server |
PACS_SERVER_TYPE | Takes either |
PACS_SERVER_URL | The URL of the PACS server. For DCM4CHEE it would be like |
UPDATE_PACS_INTEGRATION_DB | Set this to true if you want PACS Simulator automatically register itself as a modality for |
Using PACS Simulator (for test/QA purposes. Not to be used in Production)
There are two ways of uploading a DICOM image against a PACS order.
1. Manually upload DICOM Images
First find out the patient id, patient first name, patient last name and accession number of the order from modality worklist page of DCM4CHEE. Now from your terminal navigated to the bahmni-docker directory run the following command after replacing the appropriate values.
Code Block |
---|
docker compose run pacs-simulator sh -c './upload.sh DCM4CHEE@dcm4chee:11112 <PATIENT_ID> <PATIENT_FIRST_NAME> <PATIENT_LAST_NAME> <ACCESSION_NUMBER>' |
An example command would look like
docker compose run pacs-simulator sh -c './upload.sh DCM4CHEE@dcm4chee:11112 GAN203010 Test Radiology ORD-329'
2. Automated Method by running PACS-Simulator
The PACS Simulator service can also be started in a listen mode by running docker-compose --profile pacs-simulator up -d
. When pacs-simulator
profile is started, the order would be received by pacs-simulator service and a sample DICOM image will be uploaded to DCM4CHEE by pacs-simulator. And the completed order can be found in Folder
tab of DCM4CHEE and also in Oviyam viewer. Now the orders will not be visible in Modality Worklist.
❗_Note:_ When pacs-simulator is started, it will update entries in pacs_integration_db
modality table. Now when you want to receive the orders back in DCM4CHEE Modality Worklist make sure to update the modality table by running the below commands.
Code Block |
---|
docker compose stop pacs-simulator docker compose exec -it pacsdb sh psql -U ${PACS_INTEGRATION_DB_USERNAME} -d ${PACS_INTEGRATION_DB_NAME} -c "UPDATE modality set ip='dcm4chee',port=2575 where id=1;" exit |