Global: ^AUTTCOP

FileMan FileNo	FileMan Filename	Package
9999999.83	CONFIDENTIALITY POLICIES	Utility Tables

Description

DATA DICTIONARY...: This is a standard RPMS data dictionary, maintained in the AUT package. Changes to this data dictionary must be submitted to the RPMS DBA. ENTRIES IN THIS FILE...: These confidentiality policies are from the Unified Service Action Model Documentation for the clinical Area of the HL7 Reference Information Model, version 2.6, May 20, 2000. Confidentiality policies may vary from institution to institution and not all systems are capable of abiding by all details of the confidentiality policies suggested in the above table. However, these are the items that are being used in some institutions and which implementers may want to consider supporting. It is important to note that good confidentiality of the medical record can not be achieved through confidentiality codes only to filter out individual record items to certain types of users. There are two important problems with per-item confidentiality: one is inference and the other is the danger of holding back information that may be critical in a certain care situation. Inference means that filtered sensitive information can still be assumed given the other information not filtered. The simplest form of inference is that even the existence of a test order for an HIV Western Blot test or a T4/T8 lymphocyte count is a strong indication for an existing HIV infection, even if the results are not known. Very often, diagnoses can be inferred from medication, such as Zidovudin for treatment of HIV infections. The problem of hiding individual items becomes especially difficult with current medications, since the continuing administration of the medication must be assured. A similar confidentiality code attribute is therefore required in the Patient class to cover the entire patient record. But this is outside the scope of the present proposal. The flags HIV, PSY, ETH, and SDV may only be used on service items that are not patient related. Typically, they are used in the service definition object ("master" service) to indicate a generic disclosure policy of any actual service item of that type. Aggregations of data may assume the privacy level of the most private action in the aggregation. This attribute is inert with regards to the mood code. This means, the attribute primarily regulates disclosure of the information of this particular service object, regardless of its mood. However, follow-up object created in response to this object should usually carry the same or stronger protection. For example, if the order is marked sensitive then the result should be marked sensitive as well. Note that it is still forbidden to carry HIV, SDV and similar confidentiality classifiers from service definitions into patent-related data. HISTORY...: This file and initial entries created November 29, 2000, by RPMS DBA.

Fields, Total: 4

Field #	Name	Loc	Type	Details
.01	CONCEPT	0;1	FREE TEXT	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:$L(X)>30!($L(X)<1)!'(X'?1P.E) X` LAST EDITED: `NOV 29, 2000` HELP-PROMPT: `Answer must be 1-30 characters in length.` CROSS-REFERENCE: `9999999.83^B` 1)= S ^AUTTCOP("B",$E(X,1,30),DA)="" 2)= K ^AUTTCOP("B",$E(X,1,30),DA)
.02	CODE	0;2	FREE TEXT	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:$L(X)>1!($L(X)<1) X` LAST EDITED: `NOV 29, 2000` HELP-PROMPT: `Answer must be 1 character in length.`
.03	SHORT DESCRIPTION	0;3	FREE TEXT	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:$L(X)>80!($L(X)<1) X` LAST EDITED: `NOV 29, 2000` HELP-PROMPT: `Answer must be 1-80 characters in length.`
1	DEFINITION	1;0	WORD-PROCESSING #9999999.831

Customize PDF page

Package: Utility Tables

Global: ^AUTTCOP

Information

Description

Fields, Total: 4