HL7 Terminology (THO)
5.4.0 - Continuous Process Integration (ci build)
HL7 Terminology (THO) - Local Development build (v5.4.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Draft as of 2018-06-05 | Maturity Level: 1 |
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="validation-process"/>
<meta>
<lastUpdated value="2020-04-09T21:10:28.568+00:00"/>
<profile
value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"/>
</meta>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem validation-process</b></p><a name="validation-process"> </a><a name="hcvalidation-process"> </a><a name="validation-process-en-US"> </a><div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Last updated: 2020-04-09 21:10:28+0000</p><p style="margin-bottom: 0px">Profile: <a href="http://hl7.org/fhir/R4/shareablecodesystem.html">Shareable CodeSystem</a></p></div><p>This case-sensitive code system <code>http://terminology.hl7.org/CodeSystem/validation-process</code> defines the following codes:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style="white-space:nowrap">edit-check<a name="validation-process-edit-check"> </a></td><td>edit check</td><td>A method checks the healthcare resource data against predefined rules or criteria to ensure accuracy and consistency. This method helps identify common errors, such as missing or incorrect fields, by flagging data that does not conform to expected standards.</td></tr><tr><td style="white-space:nowrap">valueset<a name="validation-process-valueset"> </a></td><td>value set</td><td>A method of verification that involves comparing the data in the healthcare resource against a predefined set of allowed values or codes. This ensures that the data adheres to accepted clinical terminologies, such as SNOMED CT or ICD-10, to maintain interoperability and accuracy.</td></tr><tr><td style="white-space:nowrap">primary<a name="validation-process-primary"> </a></td><td>primary source</td><td>A verification method where the data in the healthcare resource is validated directly against the original source of the information. For example, verifying a practitioner’s license information by checking with the relevant licensing authority. This method ensures the highest level of accuracy.</td></tr><tr><td style="white-space:nowrap">multi<a name="validation-process-multi"> </a></td><td>multiple sources</td><td>A verification method where data is cross-checked against multiple independent sources to ensure its accuracy and reliability. This method reduces the likelihood of errors by confirming that the information is consistent across various trusted sources.</td></tr><tr><td style="white-space:nowrap">standalone<a name="validation-process-standalone"> </a></td><td>standalone</td><td>A method where the healthcare resource is validated independently, without relying on external data sources or systems. The data is checked internally for consistency and completeness, often used when external verification is not feasible.</td></tr><tr><td style="white-space:nowrap">in-context<a name="validation-process-in-context"> </a></td><td>in context</td><td>This method involves verifying the data within the context of its use, considering related resources and the overall scenario. For example, checking that a practitioner’s role is appropriate for the services provided at a specific location. This method ensures that the data is not only correct but also contextually relevant.</td></tr><tr><td style="white-space:nowrap">manual<a name="validation-process-manual"> </a></td><td>Manual</td><td>A verification method where human review is involved in checking the accuracy and completeness of the healthcare resource data. This process may include visual inspection, cross-referencing with physical documents, or other non-automated techniques. Manual verification is often used when automated methods are insufficient or unavailable.</td></tr><tr><td style="white-space:nowrap">attester<a name="validation-process-attester"> </a></td><td>Attester</td><td>A method where a designated individual or entity formally certifies the accuracy of the healthcare resource data. This attestation process often involves a signature or an official statement confirming that the information has been reviewed and verified as correct.</td></tr><tr><td style="white-space:nowrap">extsource<a name="validation-process-extsource"> </a></td><td>External source</td><td>Verification method where the data in the healthcare resource is validated against an independent, third-party data source. This could include external databases, registries, or authoritative organizations that provide reliable information. This method adds an extra layer of credibility by confirming data from an outside, trusted entity.</td></tr></table></div>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="pa"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
<valueInteger value="1"/>
</extension>
<url value="http://terminology.hl7.org/CodeSystem/validation-process"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.4.642.1.889"/>
</identifier>
<version value="1.0.0"/>
<name value="Validation_process"/>
<title value="Validation-process"/>
<status value="draft"/>
<experimental value="false"/>
<date value="2018-06-05T14:06:02+00:00"/>
<publisher value="Health Level Seven International"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://hl7.org"/>
</telecom>
<telecom>
<system value="email"/>
<value value="hq@HL7.org"/>
</telecom>
</contact>
<description value="The primary process by which the target is validated"/>
<copyright
value="This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license"/>
<caseSensitive value="true"/>
<valueSet
value="http://terminology.hl7.org/ValueSet/verificationresult-validation-process"/>
<content value="complete"/>
<concept>
<code value="edit-check"/>
<display value="edit check"/>
<definition
value="A method checks the healthcare resource data against predefined rules or criteria to ensure accuracy and consistency. This method helps identify common errors, such as missing or incorrect fields, by flagging data that does not conform to expected standards."/>
</concept>
<concept>
<code value="valueset"/>
<display value="value set"/>
<definition
value="A method of verification that involves comparing the data in the healthcare resource against a predefined set of allowed values or codes. This ensures that the data adheres to accepted clinical terminologies, such as SNOMED CT or ICD-10, to maintain interoperability and accuracy."/>
</concept>
<concept>
<code value="primary"/>
<display value="primary source"/>
<definition
value="A verification method where the data in the healthcare resource is validated directly against the original source of the information. For example, verifying a practitioner’s license information by checking with the relevant licensing authority. This method ensures the highest level of accuracy."/>
</concept>
<concept>
<code value="multi"/>
<display value="multiple sources"/>
<definition
value="A verification method where data is cross-checked against multiple independent sources to ensure its accuracy and reliability. This method reduces the likelihood of errors by confirming that the information is consistent across various trusted sources."/>
</concept>
<concept>
<code value="standalone"/>
<display value="standalone"/>
<definition
value="A method where the healthcare resource is validated independently, without relying on external data sources or systems. The data is checked internally for consistency and completeness, often used when external verification is not feasible."/>
</concept>
<concept>
<code value="in-context"/>
<display value="in context"/>
<definition
value="This method involves verifying the data within the context of its use, considering related resources and the overall scenario. For example, checking that a practitioner’s role is appropriate for the services provided at a specific location. This method ensures that the data is not only correct but also contextually relevant."/>
</concept>
<concept>
<code value="manual"/>
<display value="Manual"/>
<definition
value="A verification method where human review is involved in checking the accuracy and completeness of the healthcare resource data. This process may include visual inspection, cross-referencing with physical documents, or other non-automated techniques. Manual verification is often used when automated methods are insufficient or unavailable."/>
</concept>
<concept>
<code value="attester"/>
<display value="Attester"/>
<definition
value="A method where a designated individual or entity formally certifies the accuracy of the healthcare resource data. This attestation process often involves a signature or an official statement confirming that the information has been reviewed and verified as correct."/>
</concept>
<concept>
<code value="extsource"/>
<display value="External source"/>
<definition
value="Verification method where the data in the healthcare resource is validated against an independent, third-party data source. This could include external databases, registries, or authoritative organizations that provide reliable information. This method adds an extra layer of credibility by confirming data from an outside, trusted entity."/>
</concept>
</CodeSystem>