1 / 7

Slow-Speed C ollision vs. Nuclear Fusion Standards in AP

Slow-Speed C ollision vs. Nuclear Fusion Standards in AP. JD Nolen HL7 AP Co-chair. Where are we?. AP WSI Imaging ( DICOM ). Specimen/Container Identification 2D Barcode Standardization ( CLSI ) Unique Identifier ( HL7 ). APSR ( IHE ). LAW ( IHE ). Where can we go?.

tricia
Download Presentation

Slow-Speed C ollision vs. Nuclear Fusion Standards in AP

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. Slow-Speed Collision vs. Nuclear Fusion Standards in AP JD Nolen HL7 AP Co-chair

  2. Where are we? AP WSI Imaging (DICOM) • Specimen/Container Identification • 2D Barcode Standardization (CLSI) • Unique Identifier (HL7) APSR (IHE) LAW (IHE)

  3. Where can we go?

  4. But what about Supplement 145? • We need a unified standard around the storage of whole slide images • This standard powers the digital workflow • But without a standardized, interoperable workflow prior to that, we will struggle

  5. Proposed Plan • Harmonization of Unique ID (HL7) and 2D Barcode (CLSI) • Already started • F2F in Baltimore end of March • AP/O&O HL7 harmonizing Unique ID with Specimen Model….possible informative ballot in September • Potential “real estate” issue with small format of 2D standard and information in Unique

  6. Proposed Plan cont. • Joint workflow project (HL7, DICOM, IHE) • Leverage LAW profile to define standard workflows in AP • Use APSR 2.0 (via HL7 Germany) to build a generic structured report • Think CDA • Ability to handle eCC-like data • Define a standard data format and vocabulary to capture all of the data in the workflow • Processing, tasks, tracking, etc.

  7. Questions?

More Related