Stream: implementers
Topic: PDF
Grahame Grieve (Sep 28 2018 at 15:18):
Someone pointed me to this:
Grahame Grieve (Sep 28 2018 at 15:19):
I have to guess that most healthcare provider organizations and related EHR vendors still are not aware that in 2008, PDF became an international, OPEN standard (ISO 32000-1, Document Management – Portable Document Format – PDF 1.7). As such, PDF has been recognized worldwide as the most reliable, flexible, and feature-rich document format for information exchange because it supports and manages any type of file format, including structured data, text, graphics, x-rays, and video that are used in the healthcare industry. However, what saddens me is that for the past 10 years, healthcare provider organizations and related EHR vendors still are not familiar with the attributes of the DYNAMIC format of the PDF document (NOT the static format, with which all users are familiar, including the above user and EHR vendor). This is probably one reason why PDF Healthcare, a 2010 Best Practices Guide (BPG) supplemented by an Implementation Guide (IG) (i.e., PDF-H was never a proposed standard) was never accepted by the healthcare information technology industry
Grahame Grieve (Sep 28 2018 at 15:19):
from https://histalk2.com/2018/09/28/weekender-9-28-18/
Grahame Grieve (Sep 28 2018 at 15:19):
my take on this is that no one is asking...
Grahame Grieve (Sep 28 2018 at 15:19):
they reached out to HL7 back then, but no one was interested...
Michele Mottini (Sep 28 2018 at 15:23):
PDF is an horribly complex format to work with
Grahame Grieve (Sep 28 2018 at 15:24):
well, that was part of the calculus, yes
Abbie Watson (Sep 29 2018 at 03:29):
There are some nice modern PDF libraries for Node that make it all quite trivial. PDFs are treated basIcally like a <canvas> tag, and all the typical rules of DOM construction and design apply that you would use while rendering a web page.
Last updated: Apr 12 2022 at 19:14 UTC
