The classification system presently used for mortality statistics is:
A. ICD-9
B. ICD-10
C. ICD-10-CM
D. ICD-10-CM/PCS
C. ICD-10-CM
The classification system used for mortality statistics is ICD-10 (International Classification of Diseases, tenth revision). Both the underlying (primary) cause of death and non-underlying causes (other causes) are coded. ICD-9 was used between 1979 and 1998 for reporting of mortality statistics. ICD-9-CM (Clinical Modification) is usually just referred to as ICD-9 and is used for classification of diseases and procedures associated with hospitalization. ICD-9-CM was replaced with ICD-10-CM on October 1, 2015. ICD-10-CM/PCS is a transitional system.
Data should be transferred to an offsite data storage area at least:
Every 8 hours
Every 24 hours
Weekly
Monthly
Weekly
Data should be encrypted, backed up, and transferred to an offsite data storage area at least weekly. Hardware systems that are essential, including servers, routers, and internet connections, should be duplicated. All backup systems should be tested regularly, at least on a monthly basis. Because hardware and software are likely to fail at some point, redundant systems are critical. Backup is necessary to ensure that information is not lost in the event of a system breakdown or failure.
In terms of communication devices for networks, a hub:
Brings network data together
Connects networks at the data link level
Determines data’s destination
Sends data to the correct destination
Brings network data together
A hub serves as a connecting device and brings network data together. For example, a typical configuration is a hub connecting workstations, printers, and a server. A bridge connects networks at the data link level. A router determines data’s destination. Another communication device is a gateway, which is utilized to connect different networks operating under different protocols. A switch, which may comprise a router or a gateway, sends data to the correct destination.
If data stored in one provider’s cloud service must be moved back to the organization’s site and unmodified before the data can be transmitted to another cloud service, this is an example of data:
Lock-in
Corruption
De-identification
Retrieval
Lock-in
If data stored in one provider’s cloud service must be moved back to the organization’s site and unmodified before the data can be transmitted to another cloud service, this is an example of data lock-in (AKA vendor lock-in). This lack of interoperability, which prevents easy transfer of information from one vendor to another, is a problem not only with cloud services but also with many EHRs. Data lock-in may occur because of the use of proprietary technology, inadequate contractual agreements, or inadequate processes.
