xCaliber healthCare Data Mesh

Letter

Letter

Source Object: Letter

The Letter source object represents letters in the context of healthcare. These letters can include various types of correspondence, such as patient communication, referrals, medical reports, and other written documents. This source object provides information about the creation, transmission, and details of these letters.

Overview

Letters are essential for communication in healthcare, allowing providers, patients, and other stakeholders to exchange information, medical records, and instructions. The Letter source object captures important metadata and content associated with these letters.

Usage

The Letter source object serves several key purposes:

  1. Attachments: It provides information about attachments associated with the letter. These attachments may include documents, reports, or other files relevant to the letter's content.
  2. Document Details: Details related to the document, such as document type, date, description, and unique identifiers, are included.
  3. Patient Information: The patient who is the subject of the letter is identified. This ensures that the letter is associated with the correct individual's medical records.
  4. Practice and Provider: Information about the healthcare practice and provider responsible for generating the letter is recorded.
  5. Delivery Information: Details about the letter's delivery method, recipient, and status, including whether it has been acknowledged or not.
  6. Letter Content: The body of the letter, including text, subject, and other related content, is captured.
  7. Resolution: The resolution section provides information about actions taken in response to the letter, such as acknowledgments, follow-ups, and any related documents.

Letters are a fundamental means of communication in healthcare. They facilitate the exchange of medical information, referrals, and instructions, and they help ensure that healthcare professionals and patients are on the same page regarding treatment and care.

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 TypexCaliber Resource
attachmentsObjectTop Level0..*---DocumentReference--NATBD
attachments.document_typeStringTop Level0..1--"Entity", "RefPanel", "PatientDemog", "ImmHistory", "MedsList", "WhoHeightChart", "WhoWeightChart", "WhoHcChart", "CdcHeightChart", "CdcWeightChart", "CdcBmiChart", "CompMedsList", "CdcHcChart"DocumentReferencecontent[*].attachment.contentType-NATBD
attachments.entity_dateDateTimeTop Level0..1---DocumentReferencecontent[].attachment.extension[].valueDateTime-NAentity-dateTBD
attachments.entity_descriptionStringTop Level0..1---DocumentReferencecontent[].attachment.extension[].valueString-NAentity-descTBD
attachments.entity_idIntegerTop Level0..1---DocumentReferencecontent[].attachment.extension[].valueInteger-NAentity-idTBD
attachments.entity_typeIntegerTop Level0..1---DocumentReferencecontent[].attachment.extension[].valueInteger-NAentity-typeTBD
attachments.handoutStringTop Level0..1---DocumentReferencecontent[].attachment.extension[].valueString-NAhandoutTBD
attachments.idIntegerTop Level0..1---DocumentReferencecontent[*].attachment.id-NATBD
document_dateDateTimeTop Level0..1---DocumentReferencedate-NA-TBD
idIntegerTop Level0..1ID--DocumentReferenceid-NATBD
patientIntegerTop Level0..1---DocumentReferencesubject.reference-NATBD
practiceIntegerTop Level0..1---DocumentReferenceextension[*].valueReference.reference-NApracticeTBD
send_to_elation_userIntegerTop Level0..1If a letter is sent to another elation user, this will be that user's id.--DocumentReferenceextension[*].valueString-NAsend-to-elation-userTBD
sign_dateDateTimeTop Level0..1---DocumentReferenceextension[*].valueDateTime-NAsigned-dateTBD
signed_byStringTop Level0..1---DocumentReferenceextension[*].valueString-NAsigned-byTBD
tagsObjectTop Level0..*---DocumentReference--NATBD
send_to_contactObjectContained0..1---Practitioner-resourceType == PracitionerNA-TBD
send_to_contact.first_nameStringContained0..1---Practitionercontained[*].name[1].given[1]use=officialNA-TBD
send_to_contact.idIntegerContained0..1---Practitionercontained[*].id-NA-TBD
send_to_contact.last_nameStringContained0..1---Practitionercontained[*].name[2].family-NA-TBD
send_to_contact.npiStringContained0..1---Practitionercontained[].identifier[].value-NA-TBD
send_to_contact.org_nameStringContained0..1---Practitionercontained[*].extension.valueString-NAorgTBD
resolutionObjectContained0..1---Task-resourceType == TaskNA-TBD
resolution.created_dateDateTimeContained0..1The datetime when this resolution state was created.--Taskcontained[].extension[].valueDateTime-NAcreated-dateTBD
resolution.deleted_dateDateTimeContained0..1The datetime when this resolution was deleted. Should never be null because we're providing the most updated resolution.--Taskcontained[].extension[].valueDateTime-NAdeleted-dateTBD
resolution.documentIntegerContained0..1Will be the same as the id of the lab order.--Taskcontained[].extension[].valueInteger-NAdocumentTBD
resolution.idIntegerContained0..1Internal id to represent the resolution state.--Taskcontained[*].id-NA-TBD
resolution.noteStringContained0..1Any note that was added to represent why an order was cancelled.--Taskcontained[*}.note[1].text-NA-TBD
resolution.resolving_documentIntegerContained0..1If the order is fulfilled will indicate the document referenced. For lab orders will usually be a report.--Taskcontained[].extension[].valueInteger-NAresolving-documentTBD
resolution.stateStringContained0..1The resolution state of the order.-outstanding, fulfilled, cancelledTaskcontained[].extension[].valueString-NAstateTBD
send_to_contact.specialtiesObjectContained0..*---PracitionerRole-resourceType == PracitionerRoleNA-TBD
send_to_contact.specialties.idIntegerContained0..1---PracitionerRolecontained[].contained[].id-NA-TBD
send_to_contact.specialties.nameStringContained0..1---PracitionerRolecontained[].contained[].specialty[*].text-NA-TBD
bodyStringContained0..1---Communicationcontained[].payload[].contentString-NA-TBD
delivery_dateDateTimeContained0..1---Communicationcontained[*].sent-NA-TBD
delivery_methodStringContained0..1--"emr", "passport", "fax", "email", "printed", "direct"Communicationcontained[].medium[].coding[*].code-NA-TBD
direct_message_toStringContained0..1---Communicationcontained[].extension[].valueString-NAdirect-messageTBD
display_toStringContained0..1---Communicationcontained[].extension[].valueString-NAdisplayTBD
email_toStringContained0..1---Communicationcontained[].medium[].text-NA-TBD
failure_unacknowledgedBooleanContained0..1---Communicationcontained[].extension[].valueBoolean-NAfailure-unacknoledgedTBD
fax_attachmentsBooleanContained0..1---Communicationcontained[].extension[].valueString-NAfax-attachmentsTBD
fax_statusStringContained0..1--"pending","success","failed"Communicationcontained[].extension[].valueString-NAfax-statusTBD
fax_toStringContained0..1---Communicationcontained[].extension[].valueString-NAfaxTBD
is_processedBooleanContained0..1---Communicationcontained[].extension[].valueBoolean-NAprocessedTBD
letter_typeStringContained0..1--"patient_initiated","patient", "referral", "provider"Communicationcontained[].extension[].valueString-NAletter-typeTBD
send_to_nameStringContained0..1---Communicationcontained[].extension[].valueString-NAsend-to-nameTBD
subjectStringContained0..1---Communicationcontained[].extension[].valueString-NAsubjectTBD
to_numberStringContained0..1---Communicationcontained[].extension[].valueInteger-NAnumberTBD
viewed_atDateTimeContained0..1---Communicationcontained[*].received-NA-TBD
with_archiveBooleanContained0..1---Communicationcontained[].extension[].valueBoolean-NAarchiveTBD