Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DICOM_HL7_LICENSE_KEY | No | Optional license key for premium features, including cross-standard mapping (DICOM to HL7, HL7 to FHIR), Mirth channel generation, and vendor private tag decoding. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_dicom_tag | Look up any DICOM tag by group/element number or keyword. Returns tag number, name, VR, VM, description, common values, and usage notes. Accepts formats: '0010,0010', '(0010,0010)', 'PatientName', 'patient name'. |
| explain_dicom_tag | Get a detailed explanation of a DICOM tag with context, including what it is, when it's used, common values, vendor quirks (Philips, GE, Siemens), gotchas, and related tags. |
| parse_hl7_message | Parse an HL7 v2.x message into human-readable format. Returns parsed segments with field names, values, table lookups, and explanations. Supports MSH, PID, PV1, OBR, OBX, ORC, DG1, AL1, NK1, IN1, and more. |
| explain_hl7_segment | Explain what an HL7 segment does and list all its fields with positions, data types, optionality, table references, and descriptions. |
| lookup_hl7_table | Look up HL7 table values. Returns the table name and all defined values with descriptions. Example: Table 0001 = Administrative Sex. |
| map_dicom_to_hl7 | [Premium] Map DICOM tags to equivalent HL7 v2 fields. Returns corresponding HL7 segment.field, mapping notes, and data type conversions. |
| map_hl7_to_fhir | [Premium] Map HL7 v2 segments/fields to FHIR R4 resources. Returns FHIR resource, element path, ConceptMap reference, and conversion notes. |
| generate_mirth_channel | [Premium] Generate Mirth Connect channel configuration XML. Creates a channel skeleton with source/destination connectors, transformer steps, filter logic, and implementation notes. |
| validate_hl7_message | [Premium] Validate an HL7 v2.x message against the standard. Checks required fields, data types, table values, segment structure, and cross-segment consistency. |
| explain_integration_pattern | [Premium] Explain common healthcare integration patterns including message flow diagrams, trigger events, expected segments, common pitfalls, and best practices. Patterns: 'ADT feed', 'order to result', 'radiology workflow', 'lab interface', 'report distribution', 'patient merge', 'charge posting'. |
| decode_private_tags | [Premium] Decode vendor-specific private DICOM tags. Returns known private tag meaning for Philips, GE, Siemens, Fuji, Agfa, Canon/Toshiba, Hologic. |
| generate_sample_message | [Premium] Generate realistic sample HL7 messages for testing. Supports ADT^A01, ADT^A04, ADT^A08, ADT^A03, ADT^A34, ADT^A40, ORM^O01, ORU^R01, MDM^T02, SIU^S12, DFT^P03. |
| pacs_echo | [Premium] Verify PACS connectivity. Sends a C-ECHO (DIMSE) or HTTP ping (DICOMweb) to confirm the PACS server is reachable and accepting connections. Returns success/failure, response time, and connection details. |
| pacs_query | [Premium] Search PACS for studies or series. Supports filtering by patient ID, patient name, accession number, study date (YYYYMMDD or range), modality, and study description. Returns up to 50 results. Uses C-FIND (DIMSE) or QIDO-RS (DICOMweb). |
| pacs_get_metadata | [Premium] Retrieve detailed metadata for a study or series from PACS. Returns DICOM header information including patient, study, series, and equipment details. Uses WADO-RS metadata (DICOMweb) or series-level C-FIND (DIMSE). |
| pacs_retrieve | [Premium] Initiate C-MOVE to send images from PACS to a destination AE title. This moves real images across the network — use with care. Only available via DIMSE protocol. Requires DICOM_HL7_PACS_ALLOW_RETRIEVE=true. |
| pacs_study_summary | [Premium] Query a study from PACS and show its complete interoperability mapping. Returns: (1) study metadata from PACS, (2) DICOM-to-HL7 field mapping for key fields, (3) HL7-to-FHIR resource mapping, (4) a generated HL7 ORM^O01 message skeleton pre-filled with the study's actual data. This is the bridge between 'what's in PACS' and 'how do I represent it in HL7/FHIR'. Search by Study Instance UID or accession number. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |