...
- We directly talk to modalities only to create orders using HL7 standard Order message.
- There is a new PACS feed event generated to ensure creation of orders is resilient.
- Our code should not be tied to a particular HL7 version, though HAPI library relies on HL7 version to create orders. Find good way to deal with this. One way is to build a HAPI wrapper that identifies the HL7 version supported by the modality (this could even be configured in 'Modality' table to make it less intelligent but easier to use), and use relevant HAPI structures.
- No device specific code.
- Orthanc is the only new component we add to Bahmni deployment. Its added only where we need PACS integration.
- Orthanc (DICOM server) does not know about the modality. Modality auto forwards the image to Orthanc.
Database Entities
- Modality
- id, name, description, ip_address, port, timeout
- Order_Type
- id, name, modality_id
- Orders
- id, orderTypeId, order_uuid, test_name, test_uuid, result.
- OrderDetails
- id, orderId, hl7OrderRequest, hl7Response
- OrthancMarkers
- id, url, lastChangeSequence, pagelimit,
- All the atomfeed tables like markers, failed_events etc.
...