Support
Support
Everything on this page runs in your browser. Nothing you open here is uploaded, and the page makes no request of any kind carrying your data.
Inspect DICOM headers and pixel data directly in your browser. Drag and drop a
.dcm file to see tags, sequences and basic image information.
Make well-formed DICOM unique identifiers - under Pukka-J's root, under your own,
or under the 2.25 arc that needs no registration. Also checks a UID
you already have and says what is wrong with it.
Read a pipe-delimited message as a named structure - segments, fields, repetitions and components, with the field names the software itself uses. Decodes escape sequences, and says which line it broke on when a message will not parse.
Look up a tag by number or by name, with its value representation, multiplicity and whether it is retired. Also resolves a transfer syntax UID, and says whether it changed the pixels.
See what a bundle contains, and whether its references point at things it actually holds. Unresolvable references are a common reason an ingest fails and are tedious to find by eye.
Put two files side by side and see what differs in their headers. A tag one file is missing and a tag whose value differs are shown as the different problems they are, and the result can be copied into a support request.
Strip the identifying attributes and keep a file that still opens, so a study that will not route can be sent to someone who can look at it. Lists everything it changed. It does not remove anything burned into the image, and says so.
Checks the short list of things that actually stop a study routing: a missing mandatory attribute, UID syntax, a transfer syntax that disagrees with how the pixels are stored, character sets, and dimensions against the data. Not a conformance validator, and it says so.
Builds a QIDO-RS, WADO-RS or STOW-RS request and shows the DIMSE operation it corresponds to beside it - the C-FIND identifier, the level, and the four places where the correspondence breaks. Describes the standard rather than any product's support for it.
Builds a FHIR R4 search URL and explains each piece: which modifiers a parameter's type allows, where a comparison prefix goes, which direction an include walks, and what each summary mode actually returns. Warns about the defaults that quietly return the wrong set.
Checks a resource against the base specification: the resource type, required elements, primitive formats against the specification's own regular expressions, and codes in required bindings. A Bundle is checked entry by entry. Not a profile validator, and it lists what it did not look at beside every result.
Checks the three faults seen in practice: encoding characters that disagree with what the header declares, dates and timestamps that are not the digits-only format, and segments arriving in an order no message type uses. Not a conformance validator, and it lists what it did not look at beside every result.
Which FHIR element a v2 field becomes, according to the HL7 Version 2 to FHIR implementation guide - with the condition each mapping applies under, the code table its value goes through, and a link to the page it came from. A field with no agreed mapping says so instead of being filled in.
Something you need that is not here?