Digital Archiving and Preservation in Healthcare

Transcription

1 Digital Archiving and Preservation in Healthcare January 12, 2012 PASIG, Austin Robert Dick Data Center and Archive Resources Lead

2 Facilities and Resources Inpatient Hospitals Licensed Beds Partnership Hospitals 1 Outpatient facilities/specialty centers 100 Long-term care/assisted living 1 Service area NC, SC, VA Employees 25,000 Physician Practices: Clinic locations 364 Novant medical group physicians 1, Operating Revenue $3.4 billion 2010 Net Income $134 million Novant Health Utilization 2010 Admissions 123,000 ER Visits 495,000 Births 19,000 Surgeries (inpatient and outpatient) 119,000 Physician Medical Group Visits 3,700,000 Novant Health ranks 14th nationally among the Top 100 most highly integrated healthcare networks, according to SDI, Novant is the highest nationally ranked health system in the Carolinas. MedQuest Imaging consists of 77 diagnostic imaging centers, most of which are located in the Novant Health service area of North and South Carolina, Virginia and Georgia.

3 Healthcare Archiving Challenges Diagnostic Images from Radiology, and Cardiology were typically the initial problem for Healthcare relating to storage. No Common Healthcare industry LCM standards. LCM Rules vary from State to State and governing bodies. Some Federal guidelines and laws imply storage requirements to satisfy other requirements (HIPPA) but few actually require storage terms. Lack of Knowledge by primary stake holders regarding Data charter (file type, file size and file count) and application architecture. It s Clinical Turf Wars.. Vendor Driven Solutions without long term sustainability and Poor scalability Sunseting Applications orphan data. Frequent application Vendor changes resulting in data migration Increasing focus on Electronic Health Record and the large scale search needs places more focus on archive

4 Old Technology goes away 80 k to 1.4 meg 40 meg 10 meg 160 meg to 8 gig 5T 3T 256 Gig

5 Storage Archive Manager SAMFS/QFS Functionally described as Hierarchical Storage Management (HSM) Configurable up to 4 redundant copies for each file committed to archive. Storage layers can be any combination of device types and performance characteristics depending on application design requirements SSD, F/C, SATA, TAPE, SHELF Applications are presented a directory Abstraction layer which separates the underlying HSM from visibility. Connection is through TCP and in effect presents as NAS. Policy based data migration between storage layers. data migration processes are transparent to the application during storage hardware end-oflife changes. Can be as simple as a Standalone server, Shared file system, Remote pairing, or High Availability clustering with disassociated DR replication.

6 SAMFS/QFS Overview Enterprise Network SAMFS Server or Cluster Archiver 4 Releaser 3 Recycler Disk Cache # Stager # 1 2 Archive Media

7 ASM Ver SAM-Remote PHS FMC D173 /9176 Charlotte 86 mi. Winston Salem Fiber Channel Switch Fiber Channel Switch WAN Sun E-450 Sun E-450 PMT PHS Gigabit Ethernet Redundant 100mbit Ethernet Gigabit Ethernet FMC FMC PowderHorn Tape Archive PHS FMC SunFire 480 PowderHorn Tape Archive Dedicated Ether ACSLS Dedicated Ether SunFire 480 Serial Direct Copy 1 = 9840 Copy 2 = 9940 PMT Copy 3 = 9940 remote Redundant Disaster Recovery (DR) Archive backend 86 mile separation. (SAM-REMOTE) SunFire 480 Copy 1 = 9840 Copy 2 = 9940 Copy 3 = 9940 remote FMC ACSLS Serial Direct

8 Dynamic Archive Service Delivery Application Servers Application Servers Common DNS System Failure Redirection Dark Fiber interconnect ArchiveB ArchiveA Data Center 1 Data Center 2 Novant from a 20k ft. view as of June 2010 archive services 43+ applications.

9 Application Servers Dark Fiber & 10gig connect Enterprise Ethernet 6540 SATA Enterprise Ethernet SunFire V445 SunFire V T FMSAMFS01 ACCSAMFS SATA Sun Sun 100T SunFire V445 SunFire V445 FMSAMFS02 Sun Ethernet DR ACCSAMFS02 Sun Ethernet DR 6140 F/C 6140 F/C 33.6T 33.6T IP Robot Control File systems are duplicated in both data Centers. Changes are copied from one system to the other using NFS mounts. DR Risk Window 4hr or less File system scanning used for monitoring Archive.log file processing also used to close DR window. IP Robot Control SunFire X4100 Su n FMACSLS nn SunFire X4100 Su n ACCACSLS nn T10KA 8 ea T10KA 8 ea EDSI - NFS Migrator used for DR replication SAM 4.6.x

10 SunFire V445 SunFire V445 Application Servers 6540 SATA 100T Enterprise Ethernet Dark Fiber & 10gig connect Enterprise Ethernet 6540 SATA 100T 6540 SATA 100T Sun FMSAMFS02 10 gig 10 gig Sun ACCSAMFS SATA 100T 6140 F/C 33.6T SASx4 FMSAMFS01 10 gig ACCSAMFS01 SAS x F/C 33.6T 1.6T 10 gig 1.6T F5100 Flash Ether SunFire X4100 Su n FMACSLS nn File systems are duplicated in both data Centers. Changes are forwarded as inodes are modified relative to the SBdb hooks in SAM 5.2 DR Risk Window 5min. or less File system scanning verification to be used weekly SunFire X4100 Su F5100 Flash n ACCACSLS nn Ether SAM T10KB T10KB 8 ea EDSI UNIX Migrator used for DR replication 8 ea

11 Snap Shot as of Dec applications Archiving 3 Applications actively driving data to both Data Center Archive systems File types stored include; DICOM packaged and native format SOP class tagged Tif, Gif, Avi, Jpeg, Mp3, Mpeg, Mp4, iso Office application documents, Tar, ZIP, arc, rar, cab, bin, exe Acronis tib, SQL.bak, Ghost images, Rman Total File count 507 Million Consuming 603 Terabytes Largest single file system is 95 million inodes Growing at ~ 50-to-70k files/day + 1 T

12 User/Application Challenges Determining of Application performance required to meet end user expectation Getting a clear understanding of how the files will come into the system, and how they will be used/reused and how often. Can LCM be applied in any manner on the data set? Clearly defining the statistical mode size of the files to be stored, not the average! Defining the access method to be used. SAMBA Windows CIFS NFS FTP HTTP SSH, telnet, or rlogin Security of access and security of file structure POSIX file ACLs or are WINDOWS AD ACLS required Clearly Communicating performance for each HSM layer to customer /stake holders and documenting acceptance in an SLA/OLA.