xCaliber healthCare Data Mesh

Document Tag

Document Tag

Source Object: Document Tag

The Document Tag source object is used to categorize and organize healthcare documents by attaching relevant tags to them. These tags provide context and aid in document management within the healthcare system.

Overview

In healthcare systems, a vast amount of documents, such as medical records, test results, and clinical notes, need to be managed efficiently. The Document Tag source object serves as a valuable tool for categorizing and organizing these documents. Each tag is associated with specific attributes, enabling better document management.

Usage

The Document Tag source object is employed in various ways within a healthcare platform:

  1. Categorization: Tags are used to categorize documents based on their content, purpose, or relevance. This allows healthcare professionals to quickly find and access specific types of documents.
  2. Contextual Information: The code_type and concept_name fields provide essential contextual information about the tag's meaning and relevance.
  3. Document Management: Document tags facilitate efficient document management by providing a structured way to group and organize documents.
  4. Search and Retrieval: Tags enable users to search for and retrieve documents more effectively. For instance, searching for all documents related to a specific medical condition is simplified using tags.
  5. Audit Trails: Tags may be used in audit trails and document histories to track changes and access to documents.
  6. Quality Assurance: Tags can be used to identify documents relevant to quality assurance, research, or specific clinical studies.

The Document Tag source object plays a crucial role in organizing and managing healthcare documents, making it easier for healthcare professionals to access and utilize critical information.

Mapping Table

Data FieldSource Field Data TypeResource Mapping ContextSource Data Field CardinalitySource Data Field DescriptionExample ValueSource Data Field Validation RuleMapped FHIR ResourceMapped FHIR Data FieldAugmented MappingAssociated Coding SystemAssociated FHIR Data Field ExtensionMapped FHIR Data Field Type
codeStringTop Level0..1---Compositiontype.coding[*].code-NA-TBD
code_typeStringTop Level0..1--CPT, SNOMED, HL7, ICD9, LOINC, CVX, RXNORM, ICD10, CPTII, HCPCS or EL8Compositiontype.condning[*].system-NA-TBD
concept_nameStringTop Level0..1---Compositiontitle-NA-TBD
contextStringTop Level0..1--rejected, ordered or reviewedCompositionstatus-NA-TBD
created_dateDateTimeTop Level0..1---Compositionextension[*].valueDateTime-NAcreated-dateTBD
deleted_dateDateTimeTop Level0..1---Compositionextension[*].valueDateTime-NAdeleted-dateTBD
descriptionStringTop Level0..1---Compositionextension[*].valueString-NAdescTBD
idIntegerTop Level0..1---Compositionid-NA-TBD
practice_createdIntegerTop Level0..1---Compositionextension[*].valueInteger-NApractice-createdTBD
snomed_result_codeStringTop Level0..1---Compositionextension[*].valueString-NAsnomed-codeTBD
valueStringTop Level0..1---Compositionextension[*].valueString-NAvalueTBD