Privacy Building Block

Abstract [Observation: templateId Privacy Building Block Class]

Known Subclasses: Reusable Confidentiality Level Structure, Reusable Purpose Of Use Code Structure, Reusable Refrain Policy Code Structure, Reusable Obligation Policy Code Structure

This abstract class is a generic represented of a coded privacy annotation
          corresponding to confidentiality code, purpose of use, obligation, or refrain policy
          code.  This is an implementation-neutral representation of healthcare privacy
          annotation  represented as ebXML RIM metadata (e.g. XDS metadata content profile,
          XDM metadata content  profile) or CDA templates (e.g. PrivacyAnnotation,
          SecurityObservation) or security  specifications (e.g. SAML, OAuth).
            A system may decide to include specific additional privacy metadata that applies
          to data protected by specific policies.  If a query for documents is asserting a
          purpose of use, then the response should include the purpose of use for which the
          documents are allowed. It may include simply the purpose requested or a subset of those
          purposes. This approach protects the organization sending the data and makes it more
          likely that protected information can be shared if these protections are available. In
          other cases, if substance abuse treatment center sending information to another provider
          that is not subject to 42CFRPart2, then the sender must specify the obligation to
          "not redisclose" the information received because it may not be the
          local policy. Simple annotations such as an refrain from redisclsoure can be helpful for
          bridging the policy gaps among organization. For all these situations, the receiver of
          PHII (e.g. documents, messages) is responsible to meet the conditions privacy annotations
          explicitly specified by the sender.    The PrivacyBuildingBlock class is a
          representation of a security label field in the Security Label specification developed as
          described in the HL7 Healthcare Classification System (HCS). This IG includes both
          CDA-based and transport-specific representations of the conceptual Security Label

  1. SHALL contain exactly one [1..1] templateId such that it
    1. SHALL contain exactly one [1..1] @root="Privacy Building Block Class"
  2. Extends CE
  3. SHALL contain exactly one [1..1] code (CONF:16809)
    • Coded value of the privacy annotation (e.g. "N" for
                  "Normal" confidentiality).

  4. SHALL contain exactly one [1..1] valueSet (CONF:16810)
    • The OID of the coding system or value set used to encode

  5. SHALL contain exactly one [1..1] valueSetName (CONF:16811)
    • The value set is a subset of codes in a specific coding system (e.g. HL7
                  Confidentiality, LOINC, SNOMED-CT).

  6. SHALL contain exactly one [1..1] displayName (CONF:16812)
    • Display name or label associated with the "code" value (e.g. is
                  the display name "Normal" for code "N").

  7. SHALL contain exactly one [1..1] originalText (CONF:16813)
    • This is a textual representation of the code - may include a more extensive privacy
                  label to shown to the end user.