Stream: ihe
Topic: IHE(+Dicom) mime Types
Grahame Grieve (Jun 09 2018 at 20:37):
in http://build.fhir.org/endpoint-examples-general-template.json.html there's a few illegal types. I'm just extending the terminology system to validate mime types, and these have popped up as an issue.
Grahame Grieve (Jun 09 2018 at 20:39):
XDA/XDS, DICOM WADO-RS, DICOM QIDO-RS, DICOM STOW-RS, DICOM STOW-RS, DICOM WADO-URI, IHE IID
Grahame Grieve (Jun 09 2018 at 20:40):
by the time you look at this, I will have prefixed these with 'application/dicom; variant=' which will make the technically conformant but wrong. What will the correct values be. @Elliot Silver @John Moehrke (@Brian Postlethwaite )
Elliot Silver (Jun 10 2018 at 02:01):
These shouldn’t be (pseudo) mime types. These should be something akin to protocols. Some of these are relatively easy to come up with, others are more challenging: XDS has 5 transactions, with 5 different systems involved, so how do we identify each endpoint?
Grahame Grieve (Jun 10 2018 at 03:50):
I don't know. that's part of why I didn't just fix it
John Moehrke (Jun 11 2018 at 12:34):
Im with Elliot. These are not mime-types at all. Why were you trying to make them mime-types?
Grahame Grieve (Jun 11 2018 at 23:00):
I wasn't doing anything; just trying to make the existing resource valid
Grahame Grieve (Jun 11 2018 at 23:00):
@Brian Postlethwaite (is on holiday in Europe for another week)
Elliot Silver (Jun 19 2018 at 20:02):
We should add "Origin Server" to the definition (just before the dash?) of each of the DICOM endpoints in http://build.fhir.org/valueset-endpoint-connection-type.html.
I'm not sure yet on the IHE endpoints.
Last updated: Apr 12 2022 at 19:14 UTC
