Skip to main content

Posts

Showing posts from March 28, 2010

New ISO Guidelines for Protecting Electronic Health Records

BayBiotech.NET Two ISO documents recently published provide harmonized principles and guidelines for the security of electronic health records. ISO/TS 21547:2010, Health informatics – Security requirements for archiving of electronic health records – Principles covers the basic principles needed to securely preserve health records in any format for the long-term. In the document, a holistic process covering records maintenance, retention, disclosure and eventual destruction has been extensively covered. Additional guidance for implementing ISO/TS 21547 is included in technical report ISO/TR 21548:2010, Health informatics – Security requirements for archiving of electronic health records – Guidelines. This report provides complementary guidelines to ISO/TS 21547, as well as a practical method and tools for the development and management of eArchives. Main features include the retention and records maintenance for a patient for entire lifespan reaching to 100+ years regardless o

Essentials of an Effective SOP

BayBiotech.NET Standard Operating Procedures (SOP) are valuable tool that go beyond the basic procedural description of materials and methods and provide details about the appropriate precautions. A well written SOP is always a binding document in a regulatory environment and defines the details of the procedure to be followed across the board within an organization to perform a specific procedure. A well written SOP for a particular procedure should evolve with time after repeating the process under Research and Development Unit by testing the feasibility of the steps that makes it an easy to follow methods and minimizes the risks for Out of Specification reporting later on. A well evolved SOP has its origin from a simple stepwise flow chart of a complete process. If any changes are made in the process the SOP version in use must be updated by approval of the appropriate authorities and must be brought in use and supersede any other previous versions. A typical SOP contains the