Thanks for the answer, yes I placed an radiology order through:
Clinical → Selected my patient → Consultation → Orders → Radiology Orders → Selected a random one (X-ray of mandible)
I can see the order I placed through the ‘Orders’ button in Bahmni.
These are the logs of the pacsdb container (exported after I placed the order):
➜ ~ docker logs bahmni-standard-pacsdb-1
PostgreSQL Database directory appears to contain a database; Skipping initialization
LOG: incomplete startup packet
LOG: database system was shut down at 2024-08-27 08:22:26 UTC
FATAL: the database system is starting up
LOG: MultiXact member wraparound protections are now enabled
LOG: autovacuum launcher started
LOG: database system is ready to accept connections
LOG: incomplete startup packet
ERROR: relation "jbm_dual" already exists
STATEMENT: CREATE TABLE JBM_DUAL (DUMMY INTEGER, PRIMARY KEY (DUMMY))
ERROR: relation "jbm_msg_ref" already exists
STATEMENT: CREATE TABLE JBM_MSG_REF (MESSAGE_ID BIGINT, CHANNEL_ID BIGINT, TRANSACTION_ID BIGINT, STATE CHAR(1), ORD BIGINT, PAGE_ORD BIGINT, DELIVERY_COUNT INTEGER, SCHED_DELIVERY BIGINT, PRIMARY KEY(MESSAGE_ID, CHANNEL_ID))
ERROR: relation "jbm_msg_ref_tx" already exists
STATEMENT: CREATE INDEX JBM_MSG_REF_TX ON JBM_MSG_REF (TRANSACTION_ID, STATE)
ERROR: relation "jbm_msg" already exists
STATEMENT: CREATE TABLE JBM_MSG (MESSAGE_ID BIGINT, RELIABLE CHAR(1), EXPIRATION BIGINT, TIMESTAMP BIGINT, PRIORITY SMALLINT, TYPE SMALLINT, HEADERS BYTEA, PAYLOAD BYTEA, PRIMARY KEY (MESSAGE_ID))
ERROR: relation "jbm_tx" already exists
STATEMENT: CREATE TABLE JBM_TX (NODE_ID INTEGER, TRANSACTION_ID BIGINT, BRANCH_QUAL BYTEA, FORMAT_ID INTEGER, GLOBAL_TXID BYTEA, PRIMARY KEY (TRANSACTION_ID))
ERROR: relation "jbm_counter" already exists
STATEMENT: CREATE TABLE JBM_COUNTER (NAME VARCHAR(255), NEXT_ID BIGINT, PRIMARY KEY(NAME))
ERROR: relation "jbm_id_cache" already exists
STATEMENT: CREATE TABLE JBM_ID_CACHE (NODE_ID INTEGER, CNTR INTEGER, JBM_ID VARCHAR(255), PRIMARY KEY(NODE_ID, CNTR))
ERROR: duplicate key value violates unique constraint "jbm_dual_pkey"
DETAIL: Key (dummy)=(1) already exists.
STATEMENT: INSERT INTO JBM_DUAL VALUES (1)
ERROR: relation "jbm_user" already exists
STATEMENT: CREATE TABLE JBM_USER (USER_ID VARCHAR(32) NOT NULL, PASSWD VARCHAR(32) NOT NULL, CLIENTID VARCHAR(128), PRIMARY KEY(USER_ID))
ERROR: relation "jbm_role" already exists
STATEMENT: CREATE TABLE JBM_ROLE (ROLE_ID VARCHAR(32) NOT NULL, USER_ID VARCHAR(32) NOT NULL, PRIMARY KEY(USER_ID, ROLE_ID))
ERROR: duplicate key value violates unique constraint "jbm_role_pkey"
DETAIL: Key (user_id, role_id)=(john, subscriber) already exists.
STATEMENT: INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('subscriber','john')
ERROR: duplicate key value violates unique constraint "jbm_role_pkey"
DETAIL: Key (user_id, role_id)=(guest, john) already exists.
STATEMENT: INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('john','guest')
ERROR: duplicate key value violates unique constraint "jbm_role_pkey"
DETAIL: Key (user_id, role_id)=(nobody, noacc) already exists.
STATEMENT: INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('noacc','nobody')
ERROR: duplicate key value violates unique constraint "jbm_role_pkey"
DETAIL: Key (user_id, role_id)=(guest, j2ee) already exists.
STATEMENT: INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('j2ee','guest')
ERROR: duplicate key value violates unique constraint "jbm_role_pkey"
DETAIL: Key (user_id, role_id)=(dynsub, durpublisher) already exists.
STATEMENT: INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('durpublisher','dynsub')
ERROR: duplicate key value violates unique constraint "jbm_role_pkey"
DETAIL: Key (user_id, role_id)=(guest, guest) already exists.
STATEMENT: INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('guest','guest')
ERROR: duplicate key value violates unique constraint "jbm_role_pkey"
DETAIL: Key (user_id, role_id)=(john, durpublisher) already exists.
STATEMENT: INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('durpublisher','john')
ERROR: duplicate key value violates unique constraint "jbm_user_pkey"
DETAIL: Key (user_id)=(dynsub) already exists.
STATEMENT: INSERT INTO JBM_USER (USER_ID, PASSWD) VALUES ('dynsub', 'dynsub')
ERROR: duplicate key value violates unique constraint "jbm_role_pkey"
DETAIL: Key (user_id, role_id)=(dynsub, publisher) already exists.
STATEMENT: INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('publisher','dynsub')
ERROR: duplicate key value violates unique constraint "jbm_user_pkey"
DETAIL: Key (user_id)=(nobody) already exists.
STATEMENT: INSERT INTO JBM_USER (USER_ID, PASSWD) VALUES ('nobody', 'nobody')
ERROR: duplicate key value violates unique constraint "jbm_role_pkey"
DETAIL: Key (user_id, role_id)=(john, publisher) already exists.
STATEMENT: INSERT INTO JBM_ROLE (ROLE_ID, USER_ID) VALUES ('publisher','john')
ERROR: duplicate key value violates unique constraint "jbm_user_pkey"
DETAIL: Key (user_id)=(john) already exists.
STATEMENT: INSERT INTO JBM_USER (USER_ID, PASSWD, CLIENTID) VALUES ('john', 'needle', 'DurableSubscriberExample')
ERROR: duplicate key value violates unique constraint "jbm_user_pkey"
DETAIL: Key (user_id)=(j2ee) already exists.
STATEMENT: INSERT INTO JBM_USER (USER_ID, PASSWD) VALUES ('j2ee', 'j2ee')
ERROR: duplicate key value violates unique constraint "jbm_user_pkey"
DETAIL: Key (user_id)=(guest) already exists.
STATEMENT: INSERT INTO JBM_USER (USER_ID, PASSWD) VALUES ('guest', 'guest')
ERROR: relation "jbm_postoffice" already exists
STATEMENT: CREATE TABLE JBM_POSTOFFICE (POSTOFFICE_NAME VARCHAR(255), NODE_ID INTEGER, QUEUE_NAME VARCHAR(255), COND VARCHAR(1023), SELECTOR VARCHAR(1023), CHANNEL_ID BIGINT, CLUSTERED CHAR(1), ALL_NODES CHAR(1), PRIMARY KEY(POSTOFFICE_NAME, NODE_ID, QUEUE_NAME))
ERROR: relation "ht_order_details" already exists
STATEMENT: create table HT_order_details (id integer not null, hib_sess_id CHAR(36))
ERROR: relation "ht_quartz_cron_scheduler" already exists
STATEMENT: create table HT_quartz_cron_scheduler (id integer not null, hib_sess_id CHAR(36))
ERROR: relation "ht_modality" already exists
STATEMENT: create table HT_modality (id integer not null, hib_sess_id CHAR(36))
ERROR: relation "ht_order_type" already exists
STATEMENT: create table HT_order_type (id integer not null, hib_sess_id CHAR(36))
ERROR: relation "ht_test_order" already exists
STATEMENT: create table HT_test_order (id integer not null, hib_sess_id CHAR(36))
No matter what I do with orders in Bahmni, I can never see any activity in the pacsdb.
