1 / 3

Standards Based DICOM  FHIR Gateway

Standards Based DICOM  FHIR Gateway. Based purely on DICOM and FHIR No “inside knowledge” available Could be implemented with or without assistance of PACS vendor Could be a useful model in early adoption Mirrors what was done with DICOM, XDS etc.

jenna-holloway
Download Presentation

Standards Based DICOM  FHIR Gateway

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Standards Based DICOM  FHIR Gateway • Based purely on DICOM and FHIR • No “inside knowledge” available • Could be implemented with or without assistance of PACS vendor • Could be a useful model in early adoption • Mirrors what was done with DICOM, XDS etc. • Should be stateless for simplicity and scalability PACS Gateway Client DICOM FHIR

  2. FHIR “id” issue • FHIR “id” is based on guid (but loosely!) • a-z + 0-9 + “-” • Max 36 characters (whether as guid or not) • DICOM Patient ID • All characters (inc. extensions) • Max 64 characters • DICOM Study UID • OID • Max 64 characters • 1056 • >10154 • 1066

  3. What to use as “id” for a gateway? • Native Unique identifier • NO – does not obey formatting rules • Transformed Unique identifier • NO – not enough unique values • Mapped Value • NO – needs a stateful map • What else could be used?

More Related