Tuesday, October 20, 2015

Webinar: Tracking Medical Devices – How to Manage UDI Compliance Readiness

Location and Date: Orange County, CA - 4 November 2015, 11:00am-11:40am PST – Portford Solutions Group

Portford Solutions Nick & Bruce Bolton and Axcent Advanced Analytics Joe Buonomo to co-host an online event about how the rapidly changing FDA regulatory requirements affecting medical device tracking will be accommodated by Portford Solutions’ agile-based development strategy and implementation for their best-in-class SaaS solution.

The first in a series of Webinars to be held on November 4, 2015 to discuss the important regulatory requirement of coming into compliance for with the new FDA regulation for Unique Medical Device Identifier requirements. Portford Solutions will be sponsoring this first in a new Symposium series and will discuss how their current offering complies with the beginning of the FDA requirements for device tracking. Central to this offering is the creation of a Software as a Service (SaaS) platform, a cloud-based solution that is a best-in-class model for both its cost-effectiveness and ease of deployment to solve a wide range of medical device business challenges.

Portford Solutions Group is sponsoring this program, presented by two of its founders: Bruce Bolton, Executive VP – Technology and Nick Bolton, Executive VP – Consulting; Axcent Advance Analytics Joe Buonomo, CEO and VP, Business Solutions, a long-standing expert in FDA regulation and guidance and its application within the Medical Device industry.

The Medical Device Tracking Symposium Series will be covering many topics throughout this coming year related to changing government regulations, industry guidance, infrastructure and technological challenges facing us all in this industry. The Symposium series will be a prime source for many white papers, webinars, blogs and a conference on this topic and will be available from the MedDevTrack.com website, a premier site for information and access to best-in-class software serving the industry.

We Will Be Discussing:

  • What is the September 2013 FDA Final Rule on UDIs for medical devices and what does it mean for our industry?
  • What exactly is the Law (regulation) and what isn’t?
  • What are our timelines for compliance by device class and what are the expectations for compliance?
  • Anything under considerations that may affect this changing regulatory environment?
  • How can MedDevTrack and Portford Solutions help me with my compliance needs?
  • What is MedDevTrack and Portford Solutions’ plan to meet or exceed compliance requirements with their solutions?
  • Are there any publications available that I can take with me after the presentation to help further understand all of this in a deeper way?

Register Now!
The webinar is taking place on Wednesday 4 November 2015, 11:00 am- 11:40 am PST and attendance is free for this valuable presentation. Register now by clicking on the following URL: http://www.meddevtrack.com/registration.html

Tuesday, August 4, 2015

Medical Device Tracking: Rapidly Changing USA and Worldwide Regulatory Environment

The September 2013 FDA Final Rule on UDIs for medical devices is now law!


So what does this mean for Medical Device industry?

It means that imminently, medical device manufacturers will have to upgrade their labeling and packaging systems along with their data management capabilities in order to stay compliant with incoming regulations and this is independent of creating systems to meet the demands of electronic regulatory reporting to the FDA and EMHA agencies.

 

How can Portford Solutions help me with my compliance needs?

On the whole, there was little concentrated information on the state of devices provided to the patient population by the industry. Simple marketing data such as what company makes what device; sales figures of each individual implants per medical device companies; or the number of procedures done for each implant each year are readily available. Key safety and efficacy information is not readily available to the companies, regulatory agencies and the communities they serve. Industry watchdogs are concerned that little information is gathered in any one place about the potential dangers and flaws of these devices, or the complications that occur due to their implantation procedure. Revised regulations are forthcoming, to be implemented over time.

 

At Portford, our stated systems development direction for both core software and services will fill this shortcoming by providing all the requirements for medical device tracking, patient clinical data collection and regulatory reporting. In addition we will be offering advanced data analytics and predictive analysis integrated into our workflow-based medical device tracking software to report on trends in device stability, performance and providing early detection of problems with devices before they become an issue for the companies, regulatory agencies and the patient population.

So what exactly is the “Law” and what isn’t

There has been a great deal of confusion about what would be imposed by the Patient Protection and Affordable Care Act (PPACA) – (a.k.a., “Obamacare”) HR 32001 (1) passed in 2010. Think of the law as having many distinct parts. From the title alone you have the core components of Patient Protection (part of the law governing such things as increasing quality and access to information) and Affordable Care

 

At Portford, our stated systems development direction for both core software and services will fill this shortcoming by providing all the requirements for medical device tracking, patient clinical data collection and regulatory reporting. In addition we will be offering advanced data analytics and predictive analysis integrated into our workflow-based medical device tracking software to report on trends in device stability, performance and providing early detection of problems with devices before they become an issue for the companies, regulatory agencies and the patient population.

Covering both labeling and the Global UDI (GUDID) database, manufacturers need to assess their current technical capabilities – both hardware and software – and work out how much they need to do in order to comply. Within the European market, the European Commission also announced their intention to follow suit, potentially as soon as this year (2014) (2). Compliance is to begin for some companies at the end of 2014 and all companies are to be fully compliant by 2020. Many Class I devices are expected to be exempt.

So what do I have to do?

The label of a device is to bear a unique identifier, unless an alternative location is specified by the U.S. Food and Drug Administration (FDA) or unless an exception is made for a particular device or group of devices.

The unique identifier to be able to identify the device through distribution and use.

The unique identifier to include the lot or serial number, if specified by FDA.

By the FDA adoption of the UDI system it is expected that the central requirement will create a common vocabulary for reporting and enhance electronic tracking abilities. Currently, analysis of adverse event reports is limited by the fact that the specific devices involved in an incident are often not known with the required degree of specificity. Without a common vocabulary for medical devices, meaningful analysis based on data from existing voluntary systems is problematic. Reliable and consistent identification of medical devices would enable safety surveillance so that the FDA and manufacturers could better identify potential problems or device defects, and improve patient care.

The UDI is expected to improve patient safety (in part by helping to identify counterfeit products and by improving the ability of staff to distinguish between devices that are similar in appearance but serve different functions), facilitate and improve the recall process, and create efficiencies within the medical system.

In the most basic format, the UDI is a coded number registered with standards organizations, and would incorporate a variety of information, including (but not limited to) the manufacturer of the device, expiry dates, the make and model of the device, and any special attributes that the device may possess. In a medical sense, “device” refers to any product that is not pharmaceutical in nature, and while the FDA have been given approval to exempt some devices, FDA’s VP of the UDI Program, Jay Crowely (who was responsible for implementing the UDI requirements in the Act), has expressed an intent to apply the UDI to “everything until somebody gives us good reason not to”, (excluding devices which won’t need identification) (3).

So when do we have to act to meet compliance to the law?

Since the passing of the Act, there have been calls for the FDA to publish a timeline for the implementation of the UDI and that published timeline for the FDA website is presented herein:

FDA Compliance Dates for UDI Requirements

The table below outlines key compliance dates in the UDI final rule.

1 year after publication of the final rule (September 24, 2014)

The labels and packages of class III medical devices and devices licensed under the Public Health Service Act (PHS Act) must bear a UDI. § 801.20.

Dates on the labels of these devices must be formatted as required by § 801.18. Data for these devices must be submitted to the GUDID database. § 830.300.

A 1-year extension of this compliance date may be requested under § 801.55; such a request must be submitted no later than June 23, 2014.

Class III stand-alone software must provide its UDI as required by § 801.50(b).

2 years after publication of the final rule (September 24, 2015)

The labels and packages of implantable, life-supporting, and life-sustaining devices must bear a UDI. § 801.20.

Dates on the labels of these devices must be formatted as required by § 801.18.

A device that is a life-supporting or life-sustaining device that is required to be labeled with a UDI must a bear UDI as a permanent marking on the device itself if the device is intended to be used more than once and intended to be reprocessed before each use. § 801.45. Stand-alone software that is a life-supporting or life-sustaining device must provide its UDI as required by § 801.50(b).

Data for implantable, life-supporting, and life-sustaining devices that are required to be labeled with a UDI must be submitted to the GUDID database. § 830.300.

3 years after publication of the final rule (September 24, 2016)

Class III devices required to be labeled with a UDI must bear a UDI as a permanent marking on the device itself if the device is a device intended to be used more than once and intended to be reprocessed before each use. § 801.45.

The labels and packages of class II medical devices must bear a UDI. § 801.20.

Dates on the labels of these devices must be formatted as required by § 801.18.

Class II stand-alone software must provide its UDI as required by § 801.50(b).

Data for class II devices that are required to be labeled with a UDI must be submitted to the GUDID database. § 830.300.

5 years after publication of the final rule (September 24, 2018)

A class II device that is required to be labeled with a UDI must bear a UDI as a permanent marking on the device itself if the device is a device intended to be used more than once and intended to be reprocessed before each use. § 801.45.

The labels and packages of class I medical devices and devices that have not been classified into class I, class II, or class III must bear a UDI. § 801.20.

Dates on the labels of all devices, including devices that have been excepted from UDI labeling requirements, must be formatted as required by § 801.18.

Data for class I devices and devices that have not been classified into class I, class II, or class III that are required to be labeled with a UDI must be submitted to the GUDID database. § 830.300.

Class I stand-alone software must provide its UDI as required by § 801.50(b).

7 years after publication of the final rule (September 24, 2020)

Class I devices, and devices that have not been classified into class I, class II, or class III that are required to be labeled with a UDI, must a bear UDI as a permanent marking on the device itself if the device is a device intended to be used more than once and intended to be reprocessed before each use. § 801.45.

What isn’t the law? Compliance dates for all other provisions of the final rule. Except for the provisions listed above, FDA requires full compliance with the final rule as of the effective date that applies to the provision.

Well, what was in the specification of the original PPACA was the creation of a National Medical Device Registry (NMDR) but that was later dropped during the negotiations as being too intrusive at the time to be imposed upon the MedTech industry including biotech, pharma and medical devices industries and was dropped due to industry pressure related to adherence to the initial law. It is expected to be included in one of the next revisions of the PPACA. The task force for continued investigation already exists and they are working on proposals acceptable to industry, academia and regulatory professionals (4).

National Medical Device Registry (NMDR) – Rapidly Changing Regulatory Environment

Initially as proposed in HR 3200, a national medical device registry was to be established by the Department of Health and Human Services (HHS). Within the registry, devices would be listed by type, model and serial number, or some other unique identifier.

 

The registry was intended to assist HHS in evaluating the safety and effectiveness of all implantable medical devices, including all orthopedic, neurovascular, cardiovascular, ophthalmic and dental implants. It would link data provided by manufacturers to the U.S. Food and Drug Administration with outcomes data drawn from many sources, including Medicare claims data, electronic medical records and adverse event reports. The registry data and analyses would be stripped of patient information and ultimately made available to the public and the Centers for Medicare amd Medicaid Services (CMS).

The NMDR also authorized HHS to require device makers to submit “such other information as is necessary to facilitate post-market assessments of device safety and effectiveness and notification of device risks” on an annual basis.

While the registry was not ultimately included in the final version of the bill, its proposed creation is an indicator of the potential future government role and direction for tracking medical devices. It is expected that device companies will be inclined to adhere to best practice and embrace many elements of the proposed registry concept for their own use. The industry has adopted the standard for device identification that was originally proposed of its own volition.

What all this boils down to is compliance to the new regulations can occur in stages through 2020 to allow our industry to come into full compliance. Even with a published timeframe for UDI regulation compliance, there are still other regulations and guidance in the works that we have to be vigilant for. After all, the most respected industry trends publishing group, Emergo, in their past few years’ of reporting on the annual State of the Industry for the Medical Device industry find that the biggest challenge faced by the consensus of industry experts is the “Changing Regulatory Environment”.

Biggest Challenges Faced by Medical Device Companies – By Company Size

(Source: Emergo 2014 Survey – segmentation; company size by number of employees (5))


Want More Information?

Visit our web site for information on Portford's Medical Device Tracking software and services.

References

(1) http://www.gpo.gov/fdsys/pkg/BILLS-111hr3200ih/pdf/BILLS-111hr3200ih.pdf
(2) http://www.raps.org/regulatoryDetail.aspx?id=8350
(3) Joch, Alan (October 2008). "A device by any other name". Materials Management in Health Care 17 (10): 16
(4) http://www.mdepinet.org/index.php/registry-task-force/
(5) http://www.emergogroup.com/resources/research/annual-medical-device-industry-survey

Wednesday, June 10, 2015

DocuNECT v4.8.3.5 Now Released!

DocuNECT v4.8.3.5 has now been released with the following enhancements:
Technical Compatibility
  • Test new browser versions, including Microsoft Internet Explorer 11, Firefox v38.0 and Google Chrome v43.0.
  • Client tools tested in Windows v8.1.

More information, refer to our Component Compatibility guide.

Tuesday, May 26, 2015

DocuNECT System Diagnostics Connector Now Released

The System Diagnostics connector is now released for DocuNECT v4.8. This connector analyzes the current environment and identifies any issues that may effect the performance and functionality.
  • Details the station information.
  • Details connector information and identifies inactive connectors (set to Inactive or do not have any connector runs).
  • If the connectors are active, analyzes the connector logs for any errors.
  • Details the number of roles and users. Lists users who have not logged in for over 30 days.
  • Details the storage location and warns of the storage capacity is below 25%.
  • Analyzes the application logs and lists any errors found.
The information can be emailed to a group of users internally and directly to our support. This allows our support team to analyze the reports and identify potential issues before they start to impact the environment. 

This connector is free of charge so if you want to install it, then contact our support at support@portfordsolutions.com.

Tuesday, May 19, 2015

Recap EMC World 2015

EMC World 2015 has come to a close with over 12,000 attendees joining us in Las Vegas! The experience continues with EMC World Virtual where you can relive all of the highlights. Click on the link below to access the content:
EMC World Content

Medical Device Tracking - The Next Generation

Our Commitment for Best-in-Class Medical Device Management Solutions

To complement our strong expertise in Medical Device Tracking workflow development, we have been actively working to enhance our whole collection of software and service offerings to meet the rapidly changing regulatory environment facing the device industry. One of the greatest obstacles and concerns for the industry is the nascent and coming regulatory changes (1) being imposed upon the industry; the larger the company, the greater this burden is reported. In addition, there is always a core goal for providing health outcomes that meet the best practice that can be delivered for the medical community – Is what we manufacture and aid in the delivery to patients, safe and effective?

 

At Portford, our stated systems development direction for both core software and services will fill this shortcoming by providing all the requirements for medical device tracking, patient clinical data collection and regulatory reporting. In addition we will be offering advanced data analytics and predictive analysis integrated into our workflow-based medical device tracking software to report on trends in device stability, performance and providing early detection

of problems with devices before they become an issue for the companies, regulatory agencies and the patient population. From a recently published report (2) it has been determined that the 510(k) program is in need of modification to support both patient safety and efficacy concerns.

"An alarming number of new medical devices sidestep FDA approval through a system known as the 510(k) program. The FDA typically evaluates new products with stringent premarket testing (PMA), but the process can be bypassed if a manufacturer can demonstrate that its product is “substantially equivalent” to one already on the market, a new medical device can be marketed and implanted in patients without any clinical testing or review of outcomes.

 

While the 510(k) clearing process provides patients with quick access to innovations in medicine, there is an unsettling consequence: The FDA has cleared a flood of new devices without requiring manufacturers to prove their safety and effectiveness.

 

From 2005 to 2009, for example, 71 percent of the class III (highest-risk) medical devices cleared through 510(k) were later recalled over safety concerns. Criticizing the potential risks of 510(k)-cleared devices, the U.S. Government Accountability Office has urged the FDA to improve the process for medical device review. Specific actions

were suggested, and the FDA plans to fully comply starting in 2013 with full compliance 2020."

We at Portford Solutions, have both a vision and a mission, to provide the best medical device management software to fulfill your requirements to manage the optimal outcome for your patients and medical providers. We began our initiative by providing a best-in-class Medical Device Tracking software solution accessible by all the required participants from manufacturing, distribution and eventual use of the device in patients. We built our system with an expansive specification that serves as a solid platform for the addition of many new integrated modules providing all the features and services needed to meet both best practice and all regulatory requirements.

Solutions Exceeding Regulatory and Medical Community Requirements

Our current software development is focused on providing the following features to aid your company in meeting and exceeding all the requirements for medical device management and reporting. Development has been ongoing on these enhancements and will be added as modules or incorporated into the core of our solutions in the near future.
<
  • Seamless integration with the newly established FDA GUDID Webservice Database for delivery of unique, trackable device IDs. The FDA has established a unique device identification system to adequately identify medical devices through their distribution and use. When fully implemented, the label of most devices will include a unique device identifier (UDI) in human- and machine-readable form. Device labelers must also submit certain information about each device to FDA’s Global Unique Device Identification Database (GUDID). Our software will manage the registration and link to the GUDID database beginning at the manufacturing point through eventual use in patients and subsequent follow-up.
  • Cloud-based device tracking workflow integrated with manufacturing, distribution and disposition. We make sure nothing “falls through the cracks” with many integrity checks ensuring that all required tasks are performed, recorded and audited in the most secure environment that can currently be implemented.
  • Support for the tracking and reporting on the use of complex, compound medical “device” that may be made up of many components being used in patients as a single entity.
  • Integration into our workflow of industry-proven imaging repository and image analysis for disposition - from clinical trials, PMA support and post-operative monitoring. The imaging system supports pre-surgery diagnostic images, initial implant and all subsequent follow-up meeting all radiological and photographic standard and PACS compliance.
  • Predictive analytics of time-series data to support early decision about device behavior. The analytics system takes as initial input engineering tolerances, expected behavior from previous trial/use data. The model is expanded to include such factors such patient demographics and device behavior collected from both the prescribing data and medical condition reporting. The collection of this Big Data and the predictive model can be used to measure device behavior moving toward exceeding or under-performing expected device behavior.
  • The expansion of our current database model will be built on joint industry/government data standards using the harmonization of CDISC and HL7 managed by many EMR system currently in use in hospital, clinic and physician settings.
  • Our next generation release will be fully compliant for full breadth of government mandated regulations published with compliance dates published through 2020.
  • The expanded design of our system will provide an option for a subscription service to the newly defined FDA PMA reporting portal. The integration of our system and service offering will help you meet the requirements for the new FDA eMDR (electronic Medical Device Report) for electronic submission of required reports. As required, we can also help manage compliance to the Medical Device Reporting regulations supporting MedWatch form creation and submission to the FDA portal for reports.
We have a staff of experts from the medical device and pharmaceutical industries that have helped us define the specification for our expanded offerings. This group is available to provide essential services for your company including:
  • Device trial definition, management and reporting
  • Expert configuration to provide the best implementation of our system for your devices
  • Regulatory preparedness consulting
We take the active position of being leaders driving the adoption of these technologies to tackle the ever-changing regulatory demands being placed upon the industry and to support best practice for delivering the best outcome for patients.

Solutions Delivery for Today’s Market

To deliver our best-in-class solution and services, we have incorporated, into the core of our design, delivery of our solutions on a cloud-based platform. We have adopted a Software as a Service (SaaS) model providing optimal cost and operational efficiencies. We will continue to provide key components of our software for deployment using in-house (On Premise) hosted model for those not ready to adopt our full SaaS model. We welcome the opportunity to discuss our SaaS model and any of particulars about our solutions.
From a published industry study (3), companies who initially implemented cloud technology to decrease costs have also achieved a competitive advantage through implementing this technology. The study found that one out of five organizations is ahead of the curve on cloud adoption. Moreover, they are achieving a competitive advantage by using cloud-based platforms, and not just cutting costs and driving efficiency through cloud computing. The study also points out the ability to use cloud-based big data to make more informed business decisions. This study shows that many businesses are seeing those advantages now, mostly after the initial cloud deployments.
From the well-published experience of others with SaaS systems, adopting our SaaS model for medical device management offers the following benefits:
  • Lower and More Predictable Costs: SaaS technology solutions are often lower cost solutions, as they enable health care organizations to avoid the costs of purchasing expensive hardware (e.g., servers) and/or software. The costs of SaaS deployment are also more predictable than on-site technology. SaaS deployment typically requires providers to pay a fixed subscription cost (monthly or yearly). On-site deployment typically requires providers to pay for ongoing costs to support and manage on-site data servers.
  • Simpler and Robust Security: SaaS technology deployment “reduces individual maintenance responsibilities and allows even small organizations to benefit, as responsibility for maintaining security is shifted from your organization to the Cloud-based service provider.
  • Easier Upgrades and Updates: Our SaaS technology solutions allow us to make upgrades and fixes to the software without end-user involvement. Upgrades and updates to SaaS technology are less expensive and easier to deploy to our 21CFR Part11-complaint platform. Updates are typically deployed in one day; not weeks.
  • Improved Accessibility: Using a SaaS solution allows your company, medical providers and staff members to access technology from remote locations. Our Co-located and replicated systems and storage architecture ensures reliability with up-time maintained at 99.7% providing worldwide access—24 hours, 7 days a week, 365 days a year.
  • Better Data Exchange: SaaS technology solutions also enable better data exchange, as “data from many organizations are stored and processed in a more uniform way (HL7 and CDISC).”(4) You can use the technology to share information with other providers, health care organizations, and patients.
  • Scalable Solutions:Our SaaS solutions are scalable and are designed to increase capacity, performance and number of users to match your business growth.

References

(1) http://www.emergogroup.com/resources/research/annual-medical-device-industry-survey
(2) http://www.drugwatch.com/medical-devices/
(3) http://www.infoworld.com/article/2612710/cloud-computing/believe-it--the-cloud-gives-you-a-business-edge.html
(4) Executive Office of the President – President’s Council of Advisors on Science and Technology. “Report to the President Realizing the Full Potential of Health Information Technology to Improve Healthcare for Americans: The Path Forward ”, http://www.whitehouse.gov/sites/default/files/microsites/ostp/pcast-health-it-report.pdf

The New Technology Behind ApplicationXtender 8.0

ApplicationXtender (AX) 8.0 from EMC is expected to launch in Q4 of this year. Portford has been closely monitoring the progress of AX 8’s development and we can now share some of the new features and enhancements with you.

Highlights

  • Built on a brand new engine core
  • New HTML 5 viewer to support document viewing, annotation and redaction
  • Restful Services API
  • Browser-based AppGen and a new AX Admin module
Updated User Interface (UI)

  • Angular JS
  • Cross-platform
  • MVC controls
  • Customizable
Restful Services API
  • SAML Authorization
  • JSON/XML support
  • Microsoft .NET 4.5
New Image Capture
  • Captiva PixTools.NET toolkit
New Admin UI
  • Replaces old Application Generator (AppGen)/AX Admin
  • License admin
  • Groups/user permissions reports
Updated Web Application UI
  • New UI design: import, query and display
  • Cross-platform support
  • Multi-browser support: Internet Explorer, Chrome, Safari, and Firefox
Updated Web Based Administration Module
  • Create and manage AX data sources
  • Create, validate and upgrade database schema
  • Create and manage AX applications
  • Create/import and manage AX users and groups
  • Create and manage AX data types
  • Manage storage
  • Other administrative tasks