Terminology

CodeSystem:ListMode

The processing mode that applies to this list.
CodeDisplayDefinition
workingWorking ListThis list is the master list, maintained in an ongoing fashion with regular updates as the real world list it is tracking changes.
snapshotSnapshot ListThis list was prepared as a snapshot. It should not be assumed to be current.
changesChange ListA point-in-time list that shows what changes have been made or recommended. E.g. a discharge medication list showing what was added and removed during an encounter.

CodeSystem:CompositionAttestationMode

The way in which a person authenticated a composition.
CodeDisplayDefinition
personalPersonalThe person authenticated the content in their personal capacity.
professionalProfessionalThe person authenticated the content in their professional capacity.
legalLegalThe person authenticated the content and accepted legal responsibility for its content.
officialOfficialThe organization authenticated the content as consistent with their policies and procedures.

CodeSystem:ListOrderCodes

Base values for the order of the items in a list resource.
CodeDisplayDefinition
userSorted by UserThe list was sorted by a user. The criteria the user used are not specified.
systemSorted by SystemThe list was sorted by the system. The criteria the user used are not specified; define additional codes to specify a particular order (or use other defined codes).
event-dateSorted by Event DateThe list is sorted by the data of the event. This can be used when the list has items which are dates with past or future events.
entry-dateSorted by Item DateThe list is sorted by the date the item was added to the list. Note that the date added to the list is not explicit in the list itself.
prioritySorted by PriorityThe list is sorted by priority. The exact method in which priority has been determined is not specified.
alphabeticSorted AlphabeticallyThe list is sorted alphabetically by an unspecified property of the items in the list.
categorySorted by CategoryThe list is sorted categorically by an unspecified property of the items in the list.
patientSorted by PatientThe list is sorted by patient, with items for each patient grouped together.

CodeSystem:DocumentReferenceStatus

The status of the document reference.
CodeDisplayDefinition
currentCurrentThis is the current reference for this document.
supersededSupersededThis reference has been superseded by another reference.
entered-in-errorEntered in ErrorThis reference was created in error.

CodeSystem:CompositionStatus

The workflow/clinical status of the composition.
CodeDisplayDefinition
preliminaryPreliminaryThis is a preliminary composition or document (also known as initial or interim). The content may be incomplete or unverified.
finalFinalThis version of the composition is complete and verified by an appropriate person and no further work is planned. Any subsequent updates would be on a new version of the composition.
amendedAmendedThe composition content or the referenced resources have been modified (edited or added to) subsequent to being released as "final" and the composition is complete and verified by an authorized person.
entered-in-errorEntered in ErrorThe composition or document was originally created/issued in error, and this is an amendment that marks that the entire series should not be considered as valid.

CodeSystem:ListEmptyReasons

General reasons for a list to be empty. Reasons are either related to a summary list (i.e. problem or medication list) or to a workflow related list (i.e. consultation list).
CodeDisplayDefinition
nilknownNil KnownClinical judgment that there are no known items for this list after reasonable investigation. Note that this a positive statement by a clinical user, and not a default position asserted by a computer system in the lack of other information. Example uses: * For allergies: the patient or patient's agent/guardian has asserted that he/she is not aware of any allergies (NKA - nil known allergies) * For medications: the patient or patient's agent/guardian has asserted that the patient is known to be taking no medications * For diagnoses, problems and procedures: the patient or patient's agent/guardian has asserted that there is no known event to record.
notaskedNot AskedThe investigation to find out whether there are items for this list has not occurred.
withheldInformation WithheldThe content of the list was not provided due to privacy or confidentiality concerns. Note that it should not be assumed that this means that the particular information in question was withheld due to its contents - it can also be a policy decision.
unavailableUnavailableInformation to populate this list cannot be obtained; e.g. unconscious patient.
notstartedNot StartedThe work to populate this list has not yet begun.
closedClosedThis list has now closed or has ceased to be relevant or useful.

CodeSystem:DocumentRelationshipType

The type of relationship between documents.
CodeDisplayDefinition
replacesReplacesThis document logically replaces or supersedes the target document.
transformsTransformsThis document was generated by transforming the target document (e.g. format or language conversion).
signsSignsThis document is a signature of the target document.
appendsAppendsThis document adds additional information to the target document.

ValueSet: CompositionAttestationMode

The way in which a person authenticated a composition.

ValueSet: DocumentTypeValueSet

This is the code specifying the precise type of document (e.g. Pulmonary History and Physical, Discharge Summary, Ultrasound Report, etc.). The Document Type value set includes all LOINC values listed in HITSP C80 Table 2-144 Document Class Value Set Definition above used for Document Class, and all LOINC values whose SCALE is DOC in the LOINC database.

ValueSet: PracticeSettingCodeValueSet

This is the code representing the clinical specialty of the clinician or provider who interacted with, treated, or provided a service to/for the patient. The value set used for clinical specialty has been limited by HITSP to the value set reproduced from HITSP C80 Table 2-149 Clinical Specialty Value Set Definition.

ValueSet: AlternativeCodeKind

Indicates the type of use for which the code is defined.

ValueSet: DocumentClassValueSet

This is the code specifying the high-level kind of document (e.g. Prescription, Discharge Summary, Report, etc.). Note: Class code for documents comes from LOINC, and is based upon one of the following:The type of service described by the document. It is described at a very high level in Section 7.3 of the LOINC Manual. The type study performed. It was determined by identifying modalities for study reports. The section of the chart where the document is placed. It was determined from the SETs created for Claims Attachment requests.

ValueSet: DocumentSectionCodes

Document section codes (LOINC codes used in CCDA sections).

ValueSet: FacilityTypeCodeValueSet

This is the code representing the type of organizational setting where the clinical encounter, service, interaction, or treatment occurred. The value set used for Healthcare Facility Type has been defined by HITSP to be the value set reproduced from HITSP C80 Table 2-147.

ValueSet: DocumentReferenceStatus

The status of the document reference.

ValueSet: DocumentReferenceFormatCodeSet

The value set is defined to be the set of format codes defined by the IHE Technical Framework, and also including additional format codes defined by the HL7. The value set is listed in HITSP C80 Table 2-153 Format Code Value Set Definition, with additions published later by IHE as published at http://wiki.ihe.net/index.php?title=IHE_Format_Codes and with additions published later by HL7 as published at https://confluence.hl7.org/display/SD/Format+Codes+for+IHE+XDS. This is the code specifying the technical format of the document. Along with the typeCode, it should provide sufficient information to allow any potential document consumer to know if it will be able to process the document. The code shall be sufficiently specific to ensure processing/display by identifying a document encoding, structure and template. The actual list of codes here is incomplete

ValueSet: CompositionStatus

The workflow/clinical status of the composition.

ValueSet: CatalogType

The type of catalog.

ValueSet: DocumentRelationshipType

The type of relationship between documents.

ValueSet: FHIRDocumentTypeCodes

FHIR Document Codes - all LOINC codes where scale type = 'DOC'.