The document discusses vendor neutral archives (VNAs) and their role in healthcare. It begins by defining an oxymoron and what makes a VNA potentially oxymoronic. It then discusses healthcare trends driving needs for consolidated, cross-site data sharing and reviews definitions of a VNA. The document outlines typical requirements and challenges for an ideal VNA. It also discusses practical VNA implementations and how standards like DICOM, HL7, and IHE profiles can enable data sharing. Finally, it argues that a PACS vendor can provide a truly vendor neutral solution through Carestream's Vue Archive platform.
16. p.17
BPPC – Basic Patient Privacy Consent
Under which condition?
Medical documents are labeled with a Confidentiality Code
Which functional role
may access which document?
What are
disclosure rules?
17. XDS Consumer
p.18
Zero foot print client
List of Medical data
stored
Launch a web
viewer/browser to
display data
Support BPPC profile to
guaranty patient privacy
18. BPPC & XDS Consumer
p.19
Confidentiality code
defines document
access
In of emergency
user can “brake the
glass”.
Action will be traced
in the Audit Log
repository following
the ATNA profile
EMR management:As moredepartments seek access to PACS, the proper identification of patients and exams becomes anissue. Often, each department will have its own patient and exam requisition system, AccessionNumbers may or may not be used for identification, and patient and exam IDs may be assigned by
EMR management:As moredepartments seek access to PACS, the proper identification of patients and exams becomes anissue. Often, each department will have its own patient and exam requisition system, AccessionNumbers may or may not be used for identification, and patient and exam IDs may be assigned by