Validation Results for USCore

Generated Mon May 11 22:39:40 UTC 2026, FHIR version 4.0.1 for hl7.fhir.us.core#8.0.1 (canonical = http://hl7.org/fhir/us/core (history)). See Errors Only & IP

Quality Checks
Publisher Version:IG Publisher Version: v2.2.7
Publication Code:core . PackageId = hl7.fhir.us.core, Canonical = http://hl7.org/fhir/us/core
Realm Check for US:

Snomed: The IG specifies the US edition of SNOMED CT

Profiles: All OK

Language Info:This IG has no language information
Publication Request:
RelatedIgs(None Found)
  • Version 8.0.1 has already been published
  • Publication Request is for version v8.0.1 which is already published
Supressed Messages:69 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.us.core8.0.1R4http://hl7.org/fhir/us/core
... hl7.terminology.r47.1.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0
.... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0
... hl7.fhir.uv.smart-app-launch2.2.0 MR4http://hl7.org/fhir/smart-app-launchhttp://hl7.org/fhir/smart-app-launch/STU2.2
.... hl7.fhir.uv.extensions5.1.0-snapshot1 OR5http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0-snapshot1FHIR Version Mismatch. Latest Release is 5.2.0
..... hl7.terminology.r55.3.0 OR5http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0FHIR Version Mismatch. Latest Release is 7.1.0
.... hl7.terminology5.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.5.0Latest Release is 7.1.0
..... hl7.fhir.uv.extensions.r41.0.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0Latest Release is 5.2.0
... us.nlm.vsac0.24.0 MR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsac
... hl7.fhir.uv.sdc3.0.0 OR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3Latest Release is 4.0.0
.... hl7.fhir.r4.examples4.0.1 OR4http://hl7.org/fhirhttp://hl7.org/fhir/R4Latest Release is 5.0.0
... us.cdc.phinvads0.12.0 MR4http://fhir.org/packages/us.cdc.phinvadshttp://fhir.org/packages/us.cdc.phinvads
... hl7.fhir.uv.extensions.r45.2.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above)
... hl7.fhir.uv.tools.r41.1.2 MR4http://hl7.org/fhir/toolshttp://hl7.org/fhir/tools/1.1.2Internal Dependency
Templates: hl7.fhir.template#1.0.0 -> hl7.base.template#1.0.0 -> fhir.base.template#1.0.0
Related IGs:n/a
Dependent IGs:no references
Global Profiles:(none declared)
Terminology Server(s):http://tx.fhir.org/r4, https://tx-nordics.fhir.org/fhir/r4, https://tx.fhir.org/r4 (details)
HTA Analysis:All OK
R5 Dependencies:(none)
Draft Dependencies:
Modifier Extensions:(none)
Previous Version Comparison: Comparison with version 7.0.0
Comparison with version 6.1.0
Comparison with version 5.0.1
Comparison with version 4.0.0
Comparison with version 3.1.1
IPA Comparison: Comparison with version 1.1.0
IPS Comparison: n/a
Validation Flags: On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Narratives SuppressedBundle/docref-example-1, Bundle/docref-example-2, DocumentReference/discharge-summary
Summary: errors = 1, warn = 26, info = 289, broken links = 0, pinned = n/a.
FilenameErrorsWarningsHints
Build Errors01212
/scratch/repo/fsh-generated/includes000
/scratch/repo/fsh-generated/includes/fsh-link-references000
/scratch/repo/fsh-generated/includes/fsh-link-references000
/scratch/repo/fsh-generated/includes/menu000
/scratch/repo/fsh-generated/includes/menu000
/scratch/repo/fsh-generated/resources/ImplementationGuide-hl7.fhir.us.core010
/scratch/repo/input/data/README000
/scratch/repo/input/data/additional-uscdi-requirements000
/scratch/repo/input/data/addl_uscdi_choice_refs000
/scratch/repo/input/data/addl_uscdi_refs000
/scratch/repo/input/data/assessments-valuesets000
/scratch/repo/input/data/codesystem-ref-all-list000
/scratch/repo/input/data/codesystems000
/scratch/repo/input/data/dstu2-r4-table000
/scratch/repo/input/data/ig000
/scratch/repo/input/data/ms_choice_refs000
/scratch/repo/input/data/ms_refs000
/scratch/repo/input/data/new_stuff000
/scratch/repo/input/data/provenance-elements000
/scratch/repo/input/data/scopes000
/scratch/repo/input/data/source000
/scratch/repo/input/data/uscdi-examples000
/scratch/repo/input/data/uscdi-table000
/scratch/repo/input/data/uscore-sps000
/scratch/repo/input/data/valueset-ref-all-list000
/scratch/repo/input/data/vsacname-fhiruri-map000
/scratch/repo/input/examples/AHC-HRSN-item-example-68517-2001
/scratch/repo/input/examples/Device-defib000
/scratch/repo/input/examples/Device-knee000
/scratch/repo/input/examples/DiagnosticReport-bone-density-report000
/scratch/repo/input/examples/DiagnosticReport-cardiology-report000
/scratch/repo/input/examples/DiagnosticReport-chest-xray-report000
/scratch/repo/input/examples/DocumentReference-adi-dnr000
/scratch/repo/input/examples/DocumentReference-living-will000
/scratch/repo/input/examples/DocumentReference-polst000
/scratch/repo/input/examples/Observation-10-minute-apgar-color001
/scratch/repo/input/examples/Observation-10-minute-apgar-heart-rate001
/scratch/repo/input/examples/Observation-10-minute-apgar-muscle-tone001
/scratch/repo/input/examples/Observation-10-minute-apgar-reflex-irritability001
/scratch/repo/input/examples/Observation-10-minute-apgar-respiratory-effort001
/scratch/repo/input/examples/Observation-10-minute-apgar-score001
/scratch/repo/input/examples/Observation-10-minute-apgar-score-panel000
/scratch/repo/input/examples/Observation-AUDIT-C-item-example-68517-2000
/scratch/repo/input/examples/Observation-AUDIT-C-item-example-68519-8001
/scratch/repo/input/examples/Observation-AUDIT-C-item-example-68520-6001
/scratch/repo/input/examples/Observation-AUDIT-C-item-example-75626-2000
/scratch/repo/input/examples/Observation-AUDIT-C-panel-example-72109-2000
/scratch/repo/input/examples/Observation-EVS-item-example-68516-4000
/scratch/repo/input/examples/Observation-EVS-item-example-89555-7000
/scratch/repo/input/examples/Observation-EVS-panel-example-89574-8000
/scratch/repo/input/examples/Observation-HVS-item-example-88122-7001
/scratch/repo/input/examples/Observation-HVS-item-example-88123-5001
/scratch/repo/input/examples/Observation-HVS-item-example-88124-3001
/scratch/repo/input/examples/Observation-HVS-panel-example-88121-9001
/scratch/repo/input/examples/Observation-PHQ9-item-example-44250-9001
/scratch/repo/input/examples/Observation-PHQ9-item-example-44251-7001
/scratch/repo/input/examples/Observation-PHQ9-item-example-44252-5001
/scratch/repo/input/examples/Observation-PHQ9-item-example-44253-3001
/scratch/repo/input/examples/Observation-PHQ9-item-example-44254-1001
/scratch/repo/input/examples/Observation-PHQ9-item-example-44255-8001
/scratch/repo/input/examples/Observation-PHQ9-item-example-44258-2001
/scratch/repo/input/examples/Observation-PHQ9-item-example-44259-0001
/scratch/repo/input/examples/Observation-PHQ9-item-example-44260-8001
/scratch/repo/input/examples/Observation-PHQ9-item-example-44261-6001
/scratch/repo/input/examples/Observation-PHQ9-item-example-69722-7001
/scratch/repo/input/examples/Observation-PHQ9-panel-example-44249-1001
/scratch/repo/input/examples/Observation-PRAPARE-item-example-54899-0002
/scratch/repo/input/examples/Observation-PRAPARE-item-example-56051-6002
/scratch/repo/input/examples/Observation-PRAPARE-item-example-56799-0002
/scratch/repo/input/examples/Observation-PRAPARE-item-example-63512-8002
/scratch/repo/input/examples/Observation-PRAPARE-item-example-63586-2002
/scratch/repo/input/examples/Observation-PRAPARE-item-example-67875-5002
/scratch/repo/input/examples/Observation-PRAPARE-item-example-71802-3001
/scratch/repo/input/examples/Observation-PRAPARE-item-example-76437-3002
/scratch/repo/input/examples/Observation-PRAPARE-item-example-76501-6001
/scratch/repo/input/examples/Observation-PRAPARE-item-example-82589-3002
/scratch/repo/input/examples/Observation-PRAPARE-item-example-93026-3001
/scratch/repo/input/examples/Observation-PRAPARE-item-example-93027-1001
/scratch/repo/input/examples/Observation-PRAPARE-item-example-93028-9001
/scratch/repo/input/examples/Observation-PRAPARE-item-example-93029-7001
/scratch/repo/input/examples/Observation-PRAPARE-item-example-93030-5001
/scratch/repo/input/examples/Observation-PRAPARE-item-example-93033-9001
/scratch/repo/input/examples/Observation-PRAPARE-item-example-93034-7001
/scratch/repo/input/examples/Observation-PRAPARE-item-example-93035-4001
/scratch/repo/input/examples/Observation-PRAPARE-item-example-93038-8002
/scratch/repo/input/examples/Observation-PRAPARE-multiselect-item-example-32624-9-answer0002
/scratch/repo/input/examples/Observation-PRAPARE-multiselect-item-example-32624-9-answer1002
/scratch/repo/input/examples/Observation-PRAPARE-multiselect-item-example-93031-3-answer0001
/scratch/repo/input/examples/Observation-PRAPARE-multiselect-item-example-93031-3-answer1001
/scratch/repo/input/examples/Observation-PRAPARE-panel-example-93025-5001
/scratch/repo/input/examples/Observation-PRAPARE-panel-example-93039-6001
/scratch/repo/input/examples/Observation-PRAPARE-panel-example-93040-4001
/scratch/repo/input/examples/Observation-PRAPARE-panel-example-93041-2001
/scratch/repo/input/examples/Observation-PRAPARE-panel-example-93042-0001
/scratch/repo/input/examples/Observation-PRAPARE-panel-example-93043-8001
/scratch/repo/input/examples/Observation-TAPS-item-example-75889-6000
/scratch/repo/input/examples/Observation-TAPS-item-example-88037-7000
/scratch/repo/input/examples/Observation-TAPS-item-example-96842-0001
/scratch/repo/input/examples/Observation-TAPS-item-example-96843-8001
/scratch/repo/input/examples/Observation-TAPS-item-example-96844-6000
/scratch/repo/input/examples/Observation-TAPS-panel-example-96841-2000
/scratch/repo/input/examples/Observation-alcohol-use-status000
/scratch/repo/input/examples/Observation-alcoholic-drinks-per-day000
/scratch/repo/input/examples/Observation-average-blood-pressure000
/scratch/repo/input/examples/Observation-care-experience-preference000
/scratch/repo/input/examples/Observation-exercise-per-day000
/scratch/repo/input/examples/Observation-exercise-per-week000
/scratch/repo/input/examples/Observation-simple-observation-cognitive-status000
/scratch/repo/input/examples/Observation-simple-observation-disability-status000
/scratch/repo/input/examples/Observation-simple-observation-functional-status000
/scratch/repo/input/examples/Observation-simple-observation-sdoh001
/scratch/repo/input/examples/Observation-substance-use-status001
/scratch/repo/input/examples/Observation-treatment-intervention-preference000
/scratch/repo/input/examples/PractitionerRole_Practitioner_Endpoint_Bundle_Example000
/scratch/repo/input/examples/Procedure-R4-defib-implant000
/scratch/repo/input/examples/Questionnaire-AUDIT-C000
/scratch/repo/input/examples/Questionnaire-TAPS000
/scratch/repo/input/examples/Questionnaire-exercise-vital-sign000
/scratch/repo/input/examples/Questionnaire-hunger-vital-sign-example100
/scratch/repo/input/examples/Questionnaire-phq-9-example000
/scratch/repo/input/examples/Questionnaire-prapare-example000
/scratch/repo/input/examples/QuestionnaireResponse-AUDIT-C000
/scratch/repo/input/examples/QuestionnaireResponse-PRAPARE-example000
/scratch/repo/input/examples/QuestionnaireResponse-TAPS000
/scratch/repo/input/examples/QuestionnaireResponse-exercise-vital-sign000
/scratch/repo/input/examples/QuestionnaireResponse-glasgow-coma-score000
/scratch/repo/input/examples/QuestionnaireResponse-hunger-vital-sign-example000
/scratch/repo/input/examples/QuestionnaireResponse-phq-9-example000
/scratch/repo/input/examples/Specimen-example-serum-hemolyzed000
/scratch/repo/input/examples/allergyintolerance-example000
/scratch/repo/input/examples/allergyintolerance-non-pharmacologic-agent-example000
/scratch/repo/input/examples/allergyintolerance-provenance-example1000
/scratch/repo/input/examples/allergyintolerance-provenance-example2000
/scratch/repo/input/examples/at-home-in-vitro-test000
/scratch/repo/input/examples/blood-pressure000
/scratch/repo/input/examples/bmi000
/scratch/repo/input/examples/bp-data-absent000
/scratch/repo/input/examples/bundle-docref-example1000
/scratch/repo/input/examples/bundle-docref-example2000
/scratch/repo/input/examples/capillary-refill-time-nail-bed000
/scratch/repo/input/examples/careteam-example000
/scratch/repo/input/examples/colonoscopy000
/scratch/repo/input/examples/condition-SDOH-example000
/scratch/repo/input/examples/condition-duodenal-ulcer000
/scratch/repo/input/examples/condition-encounter-diagnosis-example1000
/scratch/repo/input/examples/condition-encounter-diagnosis-example2000
/scratch/repo/input/examples/coverage-example000
/scratch/repo/input/examples/diagnosticreport-cbc000
/scratch/repo/input/examples/diagnosticreport-metabolic-panel000
/scratch/repo/input/examples/documentreference-discharge-summary000
/scratch/repo/input/examples/dxa-femur-l-armass-bmd000
/scratch/repo/input/examples/dxa-femur-l-t-score-bmd000
/scratch/repo/input/examples/dxa-femur-l-z-score-bmd000
/scratch/repo/input/examples/dxa-hip-l-armass-bmd000
/scratch/repo/input/examples/dxa-hip-l-t-score-bmd000
/scratch/repo/input/examples/dxa-hip-l-z-score-bmd000
/scratch/repo/input/examples/ekg-impression000
/scratch/repo/input/examples/ekg-lead000
/scratch/repo/input/examples/encounter-1036001
/scratch/repo/input/examples/encounter-delivery000
/scratch/repo/input/examples/encounter-example-1000
/scratch/repo/input/examples/episode-summary000
/scratch/repo/input/examples/example-organization-2000
/scratch/repo/input/examples/goal-1000
/scratch/repo/input/examples/goal-sdoh-2000
/scratch/repo/input/examples/head-circumference000
/scratch/repo/input/examples/health-concern-example000
/scratch/repo/input/examples/heart-rate000
/scratch/repo/input/examples/heart-rate-rhythm000
/scratch/repo/input/examples/height000
/scratch/repo/input/examples/hl7east000
/scratch/repo/input/examples/imm-1000
/scratch/repo/input/examples/jugular-vein-distension000
/scratch/repo/input/examples/length000
/scratch/repo/input/examples/library-uscore-3.1.1-model-definition000
/scratch/repo/input/examples/library-uscore-4.0.0-model-definition000
/scratch/repo/input/examples/library-uscore-5.0.1-model-definition000
/scratch/repo/input/examples/library-uscore-6.1.0-model-definition000
/scratch/repo/input/examples/library-uscore-7.0.0-model-definition000
/scratch/repo/input/examples/library-uscore-8.0.1-model-definition000
/scratch/repo/input/examples/location-hospital000
/scratch/repo/input/examples/media-chest-xray000
/scratch/repo/input/examples/media-ekg-strip000
/scratch/repo/input/examples/medicationdispense-example010
/scratch/repo/input/examples/medicationrequest-coded-oral-axid010
/scratch/repo/input/examples/medicationrequest-contained-oral-axid000
/scratch/repo/input/examples/medicationrequest-referenced-oral-axid000
/scratch/repo/input/examples/medicationrequest-self-tylenol010
/scratch/repo/input/examples/missing-coded-data-example000
/scratch/repo/input/examples/observation-ADI-example000
/scratch/repo/input/examples/observation-cbc-erythrocytes000
/scratch/repo/input/examples/observation-cbc-hematocrit000
/scratch/repo/input/examples/observation-cbc-hemoglobin000
/scratch/repo/input/examples/observation-cbc-leukocytes000
/scratch/repo/input/examples/observation-cbc-mch000
/scratch/repo/input/examples/observation-cbc-mchc000
/scratch/repo/input/examples/observation-cbc-mcv000
/scratch/repo/input/examples/observation-cbc-platelets000
/scratch/repo/input/examples/observation-no-ADI-example000
/scratch/repo/input/examples/observation-occupation000
/scratch/repo/input/examples/observation-occupation-industry-unknown000
/scratch/repo/input/examples/observation-occupation-unknown000
/scratch/repo/input/examples/observation-pregnancy-intent000
/scratch/repo/input/examples/observation-pregnancy-status000
/scratch/repo/input/examples/observation-satO2-fiO2000
/scratch/repo/input/examples/observation-serum-bun000
/scratch/repo/input/examples/observation-serum-calcium000
/scratch/repo/input/examples/observation-serum-chloride000
/scratch/repo/input/examples/observation-serum-co2000
/scratch/repo/input/examples/observation-serum-creatinine000
/scratch/repo/input/examples/observation-serum-glucose000
/scratch/repo/input/examples/observation-serum-potassium000
/scratch/repo/input/examples/observation-serum-sodium000
/scratch/repo/input/examples/observation-xray-chest-findings000
/scratch/repo/input/examples/observation-xray-chest-impression000
/scratch/repo/input/examples/ofc-percentile000
/scratch/repo/input/examples/organization-acme-lab000
/scratch/repo/input/examples/organization-acme-payer000
/scratch/repo/input/examples/organization-holy-healthcare000
/scratch/repo/input/examples/oxygen-saturation000
/scratch/repo/input/examples/p-r-interval-ekg-lead000
/scratch/repo/input/examples/packs-years-example000
/scratch/repo/input/examples/patient-child-example000
/scratch/repo/input/examples/patient-deceased-example000
/scratch/repo/input/examples/patient-example000
/scratch/repo/input/examples/patient-infant-example000
/scratch/repo/input/examples/pediatric-bmi-example000
/scratch/repo/input/examples/pediatric-wt-example000
/scratch/repo/input/examples/practitioner-1000
/scratch/repo/input/examples/practitioner-2000
/scratch/repo/input/examples/practitioner-pharmacist000
/scratch/repo/input/examples/procedure-rehab000
/scratch/repo/input/examples/pulse-intensity-palpation000
/scratch/repo/input/examples/q-t-interval-ekg-lead000
/scratch/repo/input/examples/qrs-dur-ekg-lead000
/scratch/repo/input/examples/relatedperson-shaw-niece000
/scratch/repo/input/examples/respiratory-rate000
/scratch/repo/input/examples/saint-luke-w-endpoint000
/scratch/repo/input/examples/servicerequest-bmp000
/scratch/repo/input/examples/servicerequest-cbc000
/scratch/repo/input/examples/servicerequest-chest-xray000
/scratch/repo/input/examples/servicerequest-ekg000
/scratch/repo/input/examples/servicerequest-foodpantry-referral000
/scratch/repo/input/examples/servicerequest-rehab000
/scratch/repo/input/examples/some-day-smoker000
/scratch/repo/input/examples/specimen-example-serum000
/scratch/repo/input/examples/specimen-example-urine000
/scratch/repo/input/examples/specimen-example-whole-blood000
/scratch/repo/input/examples/temperature000
/scratch/repo/input/examples/udi-1000
/scratch/repo/input/examples/urobilinogen000
/scratch/repo/input/examples/uscore-med1010
/scratch/repo/input/examples/uscore-med2010
/scratch/repo/input/examples/weight000
/scratch/repo/input/images000
/scratch/repo/input/images/ArgoR4Meds_1000
/scratch/repo/input/images/ArgoR4Meds_3000
/scratch/repo/input/images/ArgoR4Meds_4000
/scratch/repo/input/images/DiagnosticReport_DocumentReference_Resource_Overlap000
/scratch/repo/input/images/Must_Support_AllergyIntolerance000
/scratch/repo/input/images/Must_Support_AllergyIntolerance_clinicalStatus000
/scratch/repo/input/images/Must_Support_AllergyIntolerance_code000
/scratch/repo/input/images/Must_Support_Condition_category000
/scratch/repo/input/images/Must_Support_Condition_code000
/scratch/repo/input/images/Must_Support_DiagnosticReport_category000
/scratch/repo/input/images/Must_Support_DiagnosticReport_issued000
/scratch/repo/input/images/Must_Support_DiagnosticReport_presentedForm000
/scratch/repo/input/images/Must_Support_Differential_View000
/scratch/repo/input/images/Must_Support_DocumentReference000
/scratch/repo/input/images/Must_Support_DocumentReference_category000
/scratch/repo/input/images/Must_Support_Key_View000
/scratch/repo/input/images/Must_Support_MedicationRequest.reported000
/scratch/repo/input/images/Must_Support_Observation.effective000
/scratch/repo/input/images/Must_Support_Observation.value000
/scratch/repo/input/images/Must_Support_Organization_identifier000
/scratch/repo/input/images/Must_Support_Patient_name000
/scratch/repo/input/images/Must_Support_Patient_telecom000
/scratch/repo/input/images/Must_Support_Snapshot_View000
/scratch/repo/input/images/Must_Support_vital_signs.performer000
/scratch/repo/input/images/Provenance_HIE_Multi_Org_Device000
/scratch/repo/input/images/Provenance_HIE_Single_Org_Device000
/scratch/repo/input/images/Provenance_Recon_Single_Organization000
/scratch/repo/input/images/Provenance_Recon_Workflow_Step2000
/scratch/repo/input/images/README000
/scratch/repo/input/images/USCDI000
/scratch/repo/input/images/US_Core_Growth_Path000
/scratch/repo/input/images/allergies-and-intolerances000
/scratch/repo/input/images/argo_proposed_screening_and_assessments000
/scratch/repo/input/images/basic_fhir_restful_interaction000
/scratch/repo/input/images/both-url000
/scratch/repo/input/images/care-team-members000
/scratch/repo/input/images/clinical-notes000
/scratch/repo/input/images/clinical-tests000
/scratch/repo/input/images/comparison-argo000
/scratch/repo/input/images/comparison-argo/OperationOutcome-vsac-errors000
/scratch/repo/input/images/comparison-argo/administration000
/scratch/repo/input/images/comparison-argo/administration-module-person000
/scratch/repo/input/images/comparison-argo/ansi000
/scratch/repo/input/images/comparison-argo/ansi-approved000
/scratch/repo/input/images/comparison-argo/cc0000
/scratch/repo/input/images/comparison-argo/clinical000
/scratch/repo/input/images/comparison-argo/clinicalreasoning-components-diagram000
/scratch/repo/input/images/comparison-argo/clinicalreasoning-integrating-decision-support-conversation000
/scratch/repo/input/images/comparison-argo/clinicalreasoning-integrating-decision-support-radiology-request000
/scratch/repo/input/images/comparison-argo/clinicalreasoning-integrating-decision-support-service-scenario000
/scratch/repo/input/images/comparison-argo/clinicalreasoning-integrating-decision-support-simple-request000
/scratch/repo/input/images/comparison-argo/clinicalreasoning-knowledge-artifact-components000
/scratch/repo/input/images/comparison-argo/compare-to-r3000
/scratch/repo/input/images/comparison-argo/conf-optional000
/scratch/repo/input/images/comparison-argo/conf-prohibited000
/scratch/repo/input/images/comparison-argo/conf-required000
/scratch/repo/input/images/comparison-argo/conformance000
/scratch/repo/input/images/comparison-argo/conparison-zip-marker000
/scratch/repo/input/images/comparison-argo/cross000
/scratch/repo/input/images/comparison-argo/diagnostics000
/scratch/repo/input/images/comparison-argo/download000
/scratch/repo/input/images/comparison-argo/dragon000
/scratch/repo/input/images/comparison-argo/exchange000
/scratch/repo/input/images/comparison-argo/external000
/scratch/repo/input/images/comparison-argo/extra-type000
/scratch/repo/input/images/comparison-argo/favicon000
/scratch/repo/input/images/comparison-argo/fhir000
/scratch/repo/input/images/comparison-argo/fhir-logo000
/scratch/repo/input/images/comparison-argo/fhir-logo-n000
/scratch/repo/input/images/comparison-argo/fhir-logo-www000
/scratch/repo/input/images/comparison-argo/fhir-table-scripts000
/scratch/repo/input/images/comparison-argo/fhr000
/scratch/repo/input/images/comparison-argo/financial000
/scratch/repo/input/images/comparison-argo/foundation000
/scratch/repo/input/images/comparison-argo/header-tabs000
/scratch/repo/input/images/comparison-argo/help000
/scratch/repo/input/images/comparison-argo/help16000
/scratch/repo/input/images/comparison-argo/hl7-logo000
/scratch/repo/input/images/comparison-argo/hl7logo000
/scratch/repo/input/images/comparison-argo/icon-administration000
/scratch/repo/input/images/comparison-argo/icon-change-add000
/scratch/repo/input/images/comparison-argo/icon-change-edit000
/scratch/repo/input/images/comparison-argo/icon-change-remove000
/scratch/repo/input/images/comparison-argo/icon-clinical000
/scratch/repo/input/images/comparison-argo/icon-dictionary000
/scratch/repo/input/images/comparison-argo/icon-directory000
/scratch/repo/input/images/comparison-argo/icon-documentation000
/scratch/repo/input/images/comparison-argo/icon-error000
/scratch/repo/input/images/comparison-argo/icon-example000
/scratch/repo/input/images/comparison-argo/icon-fhir-1024000
/scratch/repo/input/images/comparison-argo/icon-fhir-128000
/scratch/repo/input/images/comparison-argo/icon-fhir-16000
/scratch/repo/input/images/comparison-argo/icon-fhir-16-grey000
/scratch/repo/input/images/comparison-argo/icon-fhir-24000
/scratch/repo/input/images/comparison-argo/icon-fhir-32000
/scratch/repo/input/images/comparison-argo/icon-fhir-48000
/scratch/repo/input/images/comparison-argo/icon-fhir-64000
/scratch/repo/input/images/comparison-argo/icon-fhir-720000
/scratch/repo/input/images/comparison-argo/icon-implementation000
/scratch/repo/input/images/comparison-argo/icon-include000
/scratch/repo/input/images/comparison-argo/icon-infrastructure000
/scratch/repo/input/images/comparison-argo/icon-key000
/scratch/repo/input/images/comparison-argo/icon-list000
/scratch/repo/input/images/comparison-argo/icon-not-selected000
/scratch/repo/input/images/comparison-argo/icon-object-box000
/scratch/repo/input/images/comparison-argo/icon-page000
/scratch/repo/input/images/comparison-argo/icon-q-attachment000
/scratch/repo/input/images/comparison-argo/icon-q-boolean000
/scratch/repo/input/images/comparison-argo/icon-q-choice000
/scratch/repo/input/images/comparison-argo/icon-q-coding000
/scratch/repo/input/images/comparison-argo/icon-q-date000
/scratch/repo/input/images/comparison-argo/icon-q-datetime000
/scratch/repo/input/images/comparison-argo/icon-q-decimal000
/scratch/repo/input/images/comparison-argo/icon-q-display000
/scratch/repo/input/images/comparison-argo/icon-q-group000
/scratch/repo/input/images/comparison-argo/icon-q-integer000
/scratch/repo/input/images/comparison-argo/icon-q-item000
/scratch/repo/input/images/comparison-argo/icon-q-open-choice000
/scratch/repo/input/images/comparison-argo/icon-q-quantity000
/scratch/repo/input/images/comparison-argo/icon-q-reference000
/scratch/repo/input/images/comparison-argo/icon-q-string000
/scratch/repo/input/images/comparison-argo/icon-q-text000
/scratch/repo/input/images/comparison-argo/icon-q-time000
/scratch/repo/input/images/comparison-argo/icon-q-url000
/scratch/repo/input/images/comparison-argo/icon-qi-help000
/scratch/repo/input/images/comparison-argo/icon-qi-hidden000
/scratch/repo/input/images/comparison-argo/icon-qi-horizontal000
/scratch/repo/input/images/comparison-argo/icon-qi-instructions000
/scratch/repo/input/images/comparison-argo/icon-qi-observation000
/scratch/repo/input/images/comparison-argo/icon-qi-optional000
/scratch/repo/input/images/comparison-argo/icon-qi-readonly000
/scratch/repo/input/images/comparison-argo/icon-qi-security000
/scratch/repo/input/images/comparison-argo/icon-qi-security000
/scratch/repo/input/images/comparison-argo/icon-qi-subject000
/scratch/repo/input/images/comparison-argo/icon-qi-vertical000
/scratch/repo/input/images/comparison-argo/icon-resource000
/scratch/repo/input/images/comparison-argo/icon-selected000
/scratch/repo/input/images/comparison-argo/icon-toc000
/scratch/repo/input/images/comparison-argo/icon-warning000
/scratch/repo/input/images/comparison-argo/icon_bundle000
/scratch/repo/input/images/comparison-argo/icon_choice000
/scratch/repo/input/images/comparison-argo/icon_datatype000
/scratch/repo/input/images/comparison-argo/icon_element000
/scratch/repo/input/images/comparison-argo/icon_entry_blue000
/scratch/repo/input/images/comparison-argo/icon_extension000
/scratch/repo/input/images/comparison-argo/icon_extension_complex000
/scratch/repo/input/images/comparison-argo/icon_extension_simple000
/scratch/repo/input/images/comparison-argo/icon_fixed000
/scratch/repo/input/images/comparison-argo/icon_group000
/scratch/repo/input/images/comparison-argo/icon_modifier_extension_complex000
/scratch/repo/input/images/comparison-argo/icon_modifier_extension_simple000
/scratch/repo/input/images/comparison-argo/icon_page000
/scratch/repo/input/images/comparison-argo/icon_page-child000
/scratch/repo/input/images/comparison-argo/icon_page_n000
/scratch/repo/input/images/comparison-argo/icon_page_n_c000
/scratch/repo/input/images/comparison-argo/icon_page_n_i000
/scratch/repo/input/images/comparison-argo/icon_page_n_o000
/scratch/repo/input/images/comparison-argo/icon_page_n_p000
/scratch/repo/input/images/comparison-argo/icon_primitive000
/scratch/repo/input/images/comparison-argo/icon_profile000
/scratch/repo/input/images/comparison-argo/icon_q_item000
/scratch/repo/input/images/comparison-argo/icon_q_root000
/scratch/repo/input/images/comparison-argo/icon_reference000
/scratch/repo/input/images/comparison-argo/icon_resource000
/scratch/repo/input/images/comparison-argo/icon_reuse000
/scratch/repo/input/images/comparison-argo/icon_slice000
/scratch/repo/input/images/comparison-argo/icon_slice_item000
/scratch/repo/input/images/comparison-argo/icon_text000
/scratch/repo/input/images/comparison-argo/icon_vd_col000
/scratch/repo/input/images/comparison-argo/icon_vd_foreach000
/scratch/repo/input/images/comparison-argo/icon_vd_select000
/scratch/repo/input/images/comparison-argo/icon_vd_union000
/scratch/repo/input/images/comparison-argo/icon_vd_view000
/scratch/repo/input/images/comparison-argo/ig-r4000
/scratch/repo/input/images/comparison-argo/implsupport000
/scratch/repo/input/images/comparison-argo/index000
/scratch/repo/input/images/comparison-argo/index000
/scratch/repo/input/images/comparison-argo/information000
/scratch/repo/input/images/comparison-argo/link000
/scratch/repo/input/images/comparison-argo/linked-data000
/scratch/repo/input/images/comparison-argo/lock000
/scratch/repo/input/images/comparison-argo/logo000
/scratch/repo/input/images/comparison-argo/logo_ansinew000
/scratch/repo/input/images/comparison-argo/mappingSpaces000
/scratch/repo/input/images/comparison-argo/medication000
/scratch/repo/input/images/comparison-argo/modifier000
/scratch/repo/input/images/comparison-argo/modifier-extension-warning000
/scratch/repo/input/images/comparison-argo/mustsupport000
/scratch/repo/input/images/comparison-argo/new000
/scratch/repo/input/images/comparison-argo/normative000
/scratch/repo/input/images/comparison-argo/npm000
/scratch/repo/input/images/comparison-argo/npm16000
/scratch/repo/input/images/comparison-argo/npm24000
/scratch/repo/input/images/comparison-argo/page000
/scratch/repo/input/images/comparison-argo/page000
/scratch/repo/input/images/comparison-argo/prism000
/scratch/repo/input/images/comparison-argo/prism000
/scratch/repo/input/images/comparison-argo/publication-request000
/scratch/repo/input/images/comparison-argo/qa000
/scratch/repo/input/images/comparison-argo/reasoning000
/scratch/repo/input/images/comparison-argo/resource-groupings000
/scratch/repo/input/images/comparison-argo/rss000
/scratch/repo/input/images/comparison-argo/sd-argo-allergyintolerance-us-core-allergyintolerance000
/scratch/repo/input/images/comparison-argo/sd-argo-birthsex-us-core-birthsex000
/scratch/repo/input/images/comparison-argo/sd-argo-careplan-us-core-careplan000
/scratch/repo/input/images/comparison-argo/sd-argo-condition-us-core-condition-encounter-diagnosis000
/scratch/repo/input/images/comparison-argo/sd-argo-condition-us-core-condition-problems-health-concerns000
/scratch/repo/input/images/comparison-argo/sd-argo-device-us-core-implantable-device000
/scratch/repo/input/images/comparison-argo/sd-argo-diagnosticreport-us-core-diagnosticreport-lab000
/scratch/repo/input/images/comparison-argo/sd-argo-diagnosticreport-us-core-diagnosticreport-note000
/scratch/repo/input/images/comparison-argo/sd-argo-documentreference-us-core-documentreference000
/scratch/repo/input/images/comparison-argo/sd-argo-ethnicity-us-core-ethnicity000
/scratch/repo/input/images/comparison-argo/sd-argo-goal-us-core-goal000
/scratch/repo/input/images/comparison-argo/sd-argo-immunization-us-core-immunization000
/scratch/repo/input/images/comparison-argo/sd-argo-medication-us-core-medication000
/scratch/repo/input/images/comparison-argo/sd-argo-observationresults-us-core-observation-clinical-result000
/scratch/repo/input/images/comparison-argo/sd-argo-observationresults-us-core-observation-lab000
/scratch/repo/input/images/comparison-argo/sd-argo-patient-us-core-patient000
/scratch/repo/input/images/comparison-argo/sd-argo-procedure-us-core-procedure000
/scratch/repo/input/images/comparison-argo/sd-argo-race-us-core-race000
/scratch/repo/input/images/comparison-argo/sd-argo-smokingstatus-us-core-smokingstatus000
/scratch/repo/input/images/comparison-argo/sd-argo-vitalsigns-us-core-vital-signs000
/scratch/repo/input/images/comparison-argo/search000
/scratch/repo/input/images/comparison-argo/secpriv000
/scratch/repo/input/images/comparison-argo/security-icon-app000
/scratch/repo/input/images/comparison-argo/security-icon-fhir000
/scratch/repo/input/images/comparison-argo/security-icon-sec000
/scratch/repo/input/images/comparison-argo/security-icon-user000
/scratch/repo/input/images/comparison-argo/spec000
/scratch/repo/input/images/comparison-argo/strip000
/scratch/repo/input/images/comparison-argo/stripe000
/scratch/repo/input/images/comparison-argo/summary000
/scratch/repo/input/images/comparison-argo/target000
/scratch/repo/input/images/comparison-argo/tbl-closed000
/scratch/repo/input/images/comparison-argo/tbl-open000
/scratch/repo/input/images/comparison-argo/tbl_bck0000
/scratch/repo/input/images/comparison-argo/tbl_bck00000
/scratch/repo/input/images/comparison-argo/tbl_bck000000
/scratch/repo/input/images/comparison-argo/tbl_bck0000000
/scratch/repo/input/images/comparison-argo/tbl_bck00000000
/scratch/repo/input/images/comparison-argo/tbl_bck000000000
/scratch/repo/input/images/comparison-argo/tbl_bck0000000000
/scratch/repo/input/images/comparison-argo/tbl_bck000001000
/scratch/repo/input/images/comparison-argo/tbl_bck0000010000
/scratch/repo/input/images/comparison-argo/tbl_bck00001000
/scratch/repo/input/images/comparison-argo/tbl_bck000010000
/scratch/repo/input/images/comparison-argo/tbl_bck0000100000
/scratch/repo/input/images/comparison-argo/tbl_bck000010000000
/scratch/repo/input/images/comparison-argo/tbl_bck00001001000
/scratch/repo/input/images/comparison-argo/tbl_bck000010010000
/scratch/repo/input/images/comparison-argo/tbl_bck0000101000
/scratch/repo/input/images/comparison-argo/tbl_bck00001010000
/scratch/repo/input/images/comparison-argo/tbl_bck000011000
/scratch/repo/input/images/comparison-argo/tbl_bck0000110000
/scratch/repo/input/images/comparison-argo/tbl_bck00001100000
/scratch/repo/input/images/comparison-argo/tbl_bck0000111000
/scratch/repo/input/images/comparison-argo/tbl_bck00001110000
/scratch/repo/input/images/comparison-argo/tbl_bck000011100000
/scratch/repo/input/images/comparison-argo/tbl_bck0000111000000
/scratch/repo/input/images/comparison-argo/tbl_bck00001110000000
/scratch/repo/input/images/comparison-argo/tbl_bck0000111001000
/scratch/repo/input/images/comparison-argo/tbl_bck00001110010000
/scratch/repo/input/images/comparison-argo/tbl_bck000011101000
/scratch/repo/input/images/comparison-argo/tbl_bck0000111010000
/scratch/repo/input/images/comparison-argo/tbl_bck00001110100000
/scratch/repo/input/images/comparison-argo/tbl_bck0000111011000
/scratch/repo/input/images/comparison-argo/tbl_bck00001110110000
/scratch/repo/input/images/comparison-argo/tbl_bck00001111000
/scratch/repo/input/images/comparison-argo/tbl_bck000011110000
/scratch/repo/input/images/comparison-argo/tbl_bck0000111100000
/scratch/repo/input/images/comparison-argo/tbl_bck000011110000000
/scratch/repo/input/images/comparison-argo/tbl_bck00001111001000
/scratch/repo/input/images/comparison-argo/tbl_bck000011110010000
/scratch/repo/input/images/comparison-argo/tbl_bck0000111101000
/scratch/repo/input/images/comparison-argo/tbl_bck00001111010000
/scratch/repo/input/images/comparison-argo/tbl_bck000011111000
/scratch/repo/input/images/comparison-argo/tbl_bck0000111110000
/scratch/repo/input/images/comparison-argo/tbl_bck00001111100000
/scratch/repo/input/images/comparison-argo/tbl_bck000011111000000
/scratch/repo/input/images/comparison-argo/tbl_bck00001111101000
/scratch/repo/input/images/comparison-argo/tbl_bck000011111010000
/scratch/repo/input/images/comparison-argo/tbl_bck0000111110100000
/scratch/repo/input/images/comparison-argo/tbl_bck000011111011000
/scratch/repo/input/images/comparison-argo/tbl_bck0000111110110000
/scratch/repo/input/images/comparison-argo/tbl_bck0000111111000
/scratch/repo/input/images/comparison-argo/tbl_bck00001111110000
/scratch/repo/input/images/comparison-argo/tbl_bck000011111100000
/scratch/repo/input/images/comparison-argo/tbl_bck00001111111000
/scratch/repo/input/images/comparison-argo/tbl_bck000011111110000
/scratch/repo/input/images/comparison-argo/tbl_bck0001000
/scratch/repo/input/images/comparison-argo/tbl_bck00010000
/scratch/repo/input/images/comparison-argo/tbl_bck000100000
/scratch/repo/input/images/comparison-argo/tbl_bck00011000
/scratch/repo/input/images/comparison-argo/tbl_bck000110000
/scratch/repo/input/images/comparison-argo/tbl_bck001000
/scratch/repo/input/images/comparison-argo/tbl_bck0010000
/scratch/repo/input/images/comparison-argo/tbl_bck00100000
/scratch/repo/input/images/comparison-argo/tbl_bck001000000
/scratch/repo/input/images/comparison-argo/tbl_bck0010000000
/scratch/repo/input/images/comparison-argo/tbl_bck001001000
/scratch/repo/input/images/comparison-argo/tbl_bck0010010000
/scratch/repo/input/images/comparison-argo/tbl_bck00101000
/scratch/repo/input/images/comparison-argo/tbl_bck001010000
/scratch/repo/input/images/comparison-argo/tbl_bck0011000
/scratch/repo/input/images/comparison-argo/tbl_bck00110000
/scratch/repo/input/images/comparison-argo/tbl_bck01000
/scratch/repo/input/images/comparison-argo/tbl_bck010000
/scratch/repo/input/images/comparison-argo/tbl_bck0100000
/scratch/repo/input/images/comparison-argo/tbl_bck01000000
/scratch/repo/input/images/comparison-argo/tbl_bck0101000
/scratch/repo/input/images/comparison-argo/tbl_bck01010000
/scratch/repo/input/images/comparison-argo/tbl_bck010100000
/scratch/repo/input/images/comparison-argo/tbl_bck01011000
/scratch/repo/input/images/comparison-argo/tbl_bck010110000
/scratch/repo/input/images/comparison-argo/tbl_bck011000
/scratch/repo/input/images/comparison-argo/tbl_bck0110000
/scratch/repo/input/images/comparison-argo/tbl_bck01100000
/scratch/repo/input/images/comparison-argo/tbl_bck011000000
/scratch/repo/input/images/comparison-argo/tbl_bck0110000000
/scratch/repo/input/images/comparison-argo/tbl_bck011001000
/scratch/repo/input/images/comparison-argo/tbl_bck0110010000
/scratch/repo/input/images/comparison-argo/tbl_bck01101000
/scratch/repo/input/images/comparison-argo/tbl_bck011010000
/scratch/repo/input/images/comparison-argo/tbl_bck0110100000
/scratch/repo/input/images/comparison-argo/tbl_bck011011000
/scratch/repo/input/images/comparison-argo/tbl_bck0110110000
/scratch/repo/input/images/comparison-argo/tbl_bck01101100000
/scratch/repo/input/images/comparison-argo/tbl_bck0110111000
/scratch/repo/input/images/comparison-argo/tbl_bck01101110000
/scratch/repo/input/images/comparison-argo/tbl_bck0111000
/scratch/repo/input/images/comparison-argo/tbl_bck01110000
/scratch/repo/input/images/comparison-argo/tbl_bck011100000
/scratch/repo/input/images/comparison-argo/tbl_bck01111000
/scratch/repo/input/images/comparison-argo/tbl_bck011110000
/scratch/repo/input/images/comparison-argo/tbl_bck0111100000
/scratch/repo/input/images/comparison-argo/tbl_bck011110000000
/scratch/repo/input/images/comparison-argo/tbl_bck01111001000
/scratch/repo/input/images/comparison-argo/tbl_bck011110010000
/scratch/repo/input/images/comparison-argo/tbl_bck0111101000
/scratch/repo/input/images/comparison-argo/tbl_bck01111010000
/scratch/repo/input/images/comparison-argo/tbl_bck011111000
/scratch/repo/input/images/comparison-argo/tbl_bck0111110000
/scratch/repo/input/images/comparison-argo/tbl_bck012000
/scratch/repo/input/images/comparison-argo/tbl_bck0240000
/scratch/repo/input/images/comparison-argo/tbl_bck02400000
/scratch/repo/input/images/comparison-argo/tbl_bck0241000
/scratch/repo/input/images/comparison-argo/tbl_bck02410000
/scratch/repo/input/images/comparison-argo/tbl_bck025000
/scratch/repo/input/images/comparison-argo/tbl_bck0250000
/scratch/repo/input/images/comparison-argo/tbl_bck02500000
/scratch/repo/input/images/comparison-argo/tbl_bck025000000
/scratch/repo/input/images/comparison-argo/tbl_bck02501000
/scratch/repo/input/images/comparison-argo/tbl_bck025010000
/scratch/repo/input/images/comparison-argo/tbl_bck0250240000
/scratch/repo/input/images/comparison-argo/tbl_bck025025000
/scratch/repo/input/images/comparison-argo/tbl_bck0250250000
/scratch/repo/input/images/comparison-argo/tbl_bck02503000
/scratch/repo/input/images/comparison-argo/tbl_bck0251000
/scratch/repo/input/images/comparison-argo/tbl_bck02510000
/scratch/repo/input/images/comparison-argo/tbl_bck02512000
/scratch/repo/input/images/comparison-argo/tbl_bck0251240000
/scratch/repo/input/images/comparison-argo/tbl_bck025125000
/scratch/repo/input/images/comparison-argo/tbl_bck0251250000
/scratch/repo/input/images/comparison-argo/tbl_bck0251252000
/scratch/repo/input/images/comparison-argo/tbl_bck02513000
/scratch/repo/input/images/comparison-argo/tbl_bck03000
/scratch/repo/input/images/comparison-argo/tbl_bck0320000
/scratch/repo/input/images/comparison-argo/tbl_bck033000
/scratch/repo/input/images/comparison-argo/tbl_bck0330000
/scratch/repo/input/images/comparison-argo/tbl_bck03300000
/scratch/repo/input/images/comparison-argo/tbl_bck0331000
/scratch/repo/input/images/comparison-argo/tbl_bck03310000
/scratch/repo/input/images/comparison-argo/tbl_bck0340000
/scratch/repo/input/images/comparison-argo/tbl_bck03400000
/scratch/repo/input/images/comparison-argo/tbl_bck0341000
/scratch/repo/input/images/comparison-argo/tbl_bck03410000
/scratch/repo/input/images/comparison-argo/tbl_bck035000
/scratch/repo/input/images/comparison-argo/tbl_bck0350000
/scratch/repo/input/images/comparison-argo/tbl_bck03500000
/scratch/repo/input/images/comparison-argo/tbl_bck0350240000
/scratch/repo/input/images/comparison-argo/tbl_bck035025000
/scratch/repo/input/images/comparison-argo/tbl_bck0350250000
/scratch/repo/input/images/comparison-argo/tbl_bck03503000
/scratch/repo/input/images/comparison-argo/tbl_bck0351000
/scratch/repo/input/images/comparison-argo/tbl_bck03510000
/scratch/repo/input/images/comparison-argo/tbl_bck03512000
/scratch/repo/input/images/comparison-argo/tbl_bck0351240000
/scratch/repo/input/images/comparison-argo/tbl_bck035125000
/scratch/repo/input/images/comparison-argo/tbl_bck0351250000
/scratch/repo/input/images/comparison-argo/tbl_bck0351252000
/scratch/repo/input/images/comparison-argo/tbl_bck03513000
/scratch/repo/input/images/comparison-argo/tbl_bck04000
/scratch/repo/input/images/comparison-argo/tbl_bck040000
/scratch/repo/input/images/comparison-argo/tbl_bck0400000
/scratch/repo/input/images/comparison-argo/tbl_bck041000
/scratch/repo/input/images/comparison-argo/tbl_bck0410000
/scratch/repo/input/images/comparison-argo/tbl_bck05000
/scratch/repo/input/images/comparison-argo/tbl_bck050000
/scratch/repo/input/images/comparison-argo/tbl_bck0500000
/scratch/repo/input/images/comparison-argo/tbl_bck05040000
/scratch/repo/input/images/comparison-argo/tbl_bck0505000
/scratch/repo/input/images/comparison-argo/tbl_bck05050000
/scratch/repo/input/images/comparison-argo/tbl_bck051000
/scratch/repo/input/images/comparison-argo/tbl_bck0510000
/scratch/repo/input/images/comparison-argo/tbl_bck0512000
/scratch/repo/input/images/comparison-argo/tbl_bck05140000
/scratch/repo/input/images/comparison-argo/tbl_bck0515000
/scratch/repo/input/images/comparison-argo/tbl_bck05150000
/scratch/repo/input/images/comparison-argo/tbl_bck05152000
/scratch/repo/input/images/comparison-argo/tbl_bck1000
/scratch/repo/input/images/comparison-argo/tbl_bck10000
/scratch/repo/input/images/comparison-argo/tbl_bck100000
/scratch/repo/input/images/comparison-argo/tbl_bck1000000
/scratch/repo/input/images/comparison-argo/tbl_bck10000000
/scratch/repo/input/images/comparison-argo/tbl_bck100000000
/scratch/repo/input/images/comparison-argo/tbl_bck10001000
/scratch/repo/input/images/comparison-argo/tbl_bck100010000
/scratch/repo/input/images/comparison-argo/tbl_bck1001000
/scratch/repo/input/images/comparison-argo/tbl_bck10010000
/scratch/repo/input/images/comparison-argo/tbl_bck100100000
/scratch/repo/input/images/comparison-argo/tbl_bck1001000000
/scratch/repo/input/images/comparison-argo/tbl_bck10010000000
/scratch/repo/input/images/comparison-argo/tbl_bck1001001000
/scratch/repo/input/images/comparison-argo/tbl_bck10010010000
/scratch/repo/input/images/comparison-argo/tbl_bck100101000
/scratch/repo/input/images/comparison-argo/tbl_bck1001010000
/scratch/repo/input/images/comparison-argo/tbl_bck10011000
/scratch/repo/input/images/comparison-argo/tbl_bck100110000
/scratch/repo/input/images/comparison-argo/tbl_bck101000
/scratch/repo/input/images/comparison-argo/tbl_bck1010000
/scratch/repo/input/images/comparison-argo/tbl_bck10100000
/scratch/repo/input/images/comparison-argo/tbl_bck101000000
/scratch/repo/input/images/comparison-argo/tbl_bck10101000
/scratch/repo/input/images/comparison-argo/tbl_bck101010000
/scratch/repo/input/images/comparison-argo/tbl_bck1011000
/scratch/repo/input/images/comparison-argo/tbl_bck10110000
/scratch/repo/input/images/comparison-argo/tbl_bck101100000
/scratch/repo/input/images/comparison-argo/tbl_bck1011000000
/scratch/repo/input/images/comparison-argo/tbl_bck10110000000
/scratch/repo/input/images/comparison-argo/tbl_bck1011001000
/scratch/repo/input/images/comparison-argo/tbl_bck10110010000
/scratch/repo/input/images/comparison-argo/tbl_bck101101000
/scratch/repo/input/images/comparison-argo/tbl_bck1011010000
/scratch/repo/input/images/comparison-argo/tbl_bck10111000
/scratch/repo/input/images/comparison-argo/tbl_bck101110000
/scratch/repo/input/images/comparison-argo/tbl_bck1011100000
/scratch/repo/input/images/comparison-argo/tbl_bck101111000
/scratch/repo/input/images/comparison-argo/tbl_bck1011110000
/scratch/repo/input/images/comparison-argo/tbl_bck10120000
/scratch/repo/input/images/comparison-argo/tbl_bck1013000
/scratch/repo/input/images/comparison-argo/tbl_bck10130000
/scratch/repo/input/images/comparison-argo/tbl_bck10240000
/scratch/repo/input/images/comparison-argo/tbl_bck1025000
/scratch/repo/input/images/comparison-argo/tbl_bck10250000
/scratch/repo/input/images/comparison-argo/tbl_bck103000
/scratch/repo/input/images/comparison-argo/tbl_bck1040000
/scratch/repo/input/images/comparison-argo/tbl_bck105000
/scratch/repo/input/images/comparison-argo/tbl_bck1050000
/scratch/repo/input/images/comparison-argo/tbl_bck11000
/scratch/repo/input/images/comparison-argo/tbl_bck110000
/scratch/repo/input/images/comparison-argo/tbl_bck1100000
/scratch/repo/input/images/comparison-argo/tbl_bck11000000
/scratch/repo/input/images/comparison-argo/tbl_bck110000000
/scratch/repo/input/images/comparison-argo/tbl_bck11001000
/scratch/repo/input/images/comparison-argo/tbl_bck110010000
/scratch/repo/input/images/comparison-argo/tbl_bck1101000
/scratch/repo/input/images/comparison-argo/tbl_bck11010000
/scratch/repo/input/images/comparison-argo/tbl_bck110100000
/scratch/repo/input/images/comparison-argo/tbl_bck11011000
/scratch/repo/input/images/comparison-argo/tbl_bck110110000
/scratch/repo/input/images/comparison-argo/tbl_bck111000
/scratch/repo/input/images/comparison-argo/tbl_bck1110000
/scratch/repo/input/images/comparison-argo/tbl_bck11100000
/scratch/repo/input/images/comparison-argo/tbl_bck111000000
/scratch/repo/input/images/comparison-argo/tbl_bck11101000
/scratch/repo/input/images/comparison-argo/tbl_bck111010000
/scratch/repo/input/images/comparison-argo/tbl_bck1111000
/scratch/repo/input/images/comparison-argo/tbl_bck11110000
/scratch/repo/input/images/comparison-argo/tbl_bck111100000
/scratch/repo/input/images/comparison-argo/tbl_bck1111000000
/scratch/repo/input/images/comparison-argo/tbl_bck111101000
/scratch/repo/input/images/comparison-argo/tbl_bck1111010000
/scratch/repo/input/images/comparison-argo/tbl_bck11111000
/scratch/repo/input/images/comparison-argo/tbl_bck111110000
/scratch/repo/input/images/comparison-argo/tbl_bck112000
/scratch/repo/input/images/comparison-argo/tbl_bck1120000
/scratch/repo/input/images/comparison-argo/tbl_bck11240000
/scratch/repo/input/images/comparison-argo/tbl_bck1125000
/scratch/repo/input/images/comparison-argo/tbl_bck11250000
/scratch/repo/input/images/comparison-argo/tbl_bck11252000
/scratch/repo/input/images/comparison-argo/tbl_bck113000
/scratch/repo/input/images/comparison-argo/tbl_bck1130000
/scratch/repo/input/images/comparison-argo/tbl_bck1140000
/scratch/repo/input/images/comparison-argo/tbl_bck115000
/scratch/repo/input/images/comparison-argo/tbl_bck1150000
/scratch/repo/input/images/comparison-argo/tbl_bck1152000
/scratch/repo/input/images/comparison-argo/tbl_bck12000
/scratch/repo/input/images/comparison-argo/tbl_bck120000
/scratch/repo/input/images/comparison-argo/tbl_bck124000
/scratch/repo/input/images/comparison-argo/tbl_bck1240000
/scratch/repo/input/images/comparison-argo/tbl_bck12400000
/scratch/repo/input/images/comparison-argo/tbl_bck1241000
/scratch/repo/input/images/comparison-argo/tbl_bck12410000
/scratch/repo/input/images/comparison-argo/tbl_bck125000
/scratch/repo/input/images/comparison-argo/tbl_bck1250000
/scratch/repo/input/images/comparison-argo/tbl_bck12500000
/scratch/repo/input/images/comparison-argo/tbl_bck1251000
/scratch/repo/input/images/comparison-argo/tbl_bck12510000
/scratch/repo/input/images/comparison-argo/tbl_bck125100000
/scratch/repo/input/images/comparison-argo/tbl_bck12511000
/scratch/repo/input/images/comparison-argo/tbl_bck125110000
/scratch/repo/input/images/comparison-argo/tbl_bck12512000
/scratch/repo/input/images/comparison-argo/tbl_bck1252000
/scratch/repo/input/images/comparison-argo/tbl_bck13000
/scratch/repo/input/images/comparison-argo/tbl_bck130000
/scratch/repo/input/images/comparison-argo/tbl_bck1320000
/scratch/repo/input/images/comparison-argo/tbl_bck133000
/scratch/repo/input/images/comparison-argo/tbl_bck1330000
/scratch/repo/input/images/comparison-argo/tbl_bck134000
/scratch/repo/input/images/comparison-argo/tbl_bck14000
/scratch/repo/input/images/comparison-argo/tbl_bck140000
/scratch/repo/input/images/comparison-argo/tbl_bck1400000
/scratch/repo/input/images/comparison-argo/tbl_bck141000
/scratch/repo/input/images/comparison-argo/tbl_bck1410000
/scratch/repo/input/images/comparison-argo/tbl_bck1424000
/scratch/repo/input/images/comparison-argo/tbl_bck143000
/scratch/repo/input/images/comparison-argo/tbl_bck15000
/scratch/repo/input/images/comparison-argo/tbl_bck150000
/scratch/repo/input/images/comparison-argo/tbl_bck1500000
/scratch/repo/input/images/comparison-argo/tbl_bck15040000
/scratch/repo/input/images/comparison-argo/tbl_bck1505000
/scratch/repo/input/images/comparison-argo/tbl_bck15050000
/scratch/repo/input/images/comparison-argo/tbl_bck151000
/scratch/repo/input/images/comparison-argo/tbl_bck1510000
/scratch/repo/input/images/comparison-argo/tbl_bck1512000
/scratch/repo/input/images/comparison-argo/tbl_bck15140000
/scratch/repo/input/images/comparison-argo/tbl_bck1515000
/scratch/repo/input/images/comparison-argo/tbl_bck15150000
/scratch/repo/input/images/comparison-argo/tbl_bck15152000
/scratch/repo/input/images/comparison-argo/tbl_bck152000
/scratch/repo/input/images/comparison-argo/tbl_bck1540000
/scratch/repo/input/images/comparison-argo/tbl_bck15424000
/scratch/repo/input/images/comparison-argo/tbl_bck1543000
/scratch/repo/input/images/comparison-argo/tbl_bck155000
/scratch/repo/input/images/comparison-argo/tbl_bck1550000
/scratch/repo/input/images/comparison-argo/tbl_bck1552000
/scratch/repo/input/images/comparison-argo/tbl_blank000
/scratch/repo/input/images/comparison-argo/tbl_spacer000
/scratch/repo/input/images/comparison-argo/tbl_vjoin000
/scratch/repo/input/images/comparison-argo/tbl_vjoin-closed000
/scratch/repo/input/images/comparison-argo/tbl_vjoin-open000
/scratch/repo/input/images/comparison-argo/tbl_vjoin_end000
/scratch/repo/input/images/comparison-argo/tbl_vjoin_end-closed000
/scratch/repo/input/images/comparison-argo/tbl_vjoin_end-open000
/scratch/repo/input/images/comparison-argo/tbl_vjoin_end_slice000
/scratch/repo/input/images/comparison-argo/tbl_vjoin_end_slice-closed000
/scratch/repo/input/images/comparison-argo/tbl_vjoin_end_slice-open000
/scratch/repo/input/images/comparison-argo/tbl_vjoin_end_slicer000
/scratch/repo/input/images/comparison-argo/tbl_vjoin_end_slicer-closed000
/scratch/repo/input/images/comparison-argo/tbl_vjoin_end_slicer-open000
/scratch/repo/input/images/comparison-argo/tbl_vjoin_slice000
/scratch/repo/input/images/comparison-argo/tbl_vjoin_slice-closed000
/scratch/repo/input/images/comparison-argo/tbl_vjoin_slice-open000
/scratch/repo/input/images/comparison-argo/tbl_vjoin_slicer000
/scratch/repo/input/images/comparison-argo/tbl_vjoin_slicer-closed000
/scratch/repo/input/images/comparison-argo/tbl_vjoin_slicer-open000
/scratch/repo/input/images/comparison-argo/tbl_vline000
/scratch/repo/input/images/comparison-argo/tbl_vline_slice000
/scratch/repo/input/images/comparison-argo/tbl_vline_slicer000
/scratch/repo/input/images/comparison-argo/terminology000
/scratch/repo/input/images/comparison-argo/tick000
/scratch/repo/input/images/comparison-argo/tick2000
/scratch/repo/input/images/comparison-argo/validation-oo000
/scratch/repo/input/images/comparison-argo/validation-summary000
/scratch/repo/input/images/comparison-argo/vs-c80-doc-typecodes-us-core-documentreference-type000
/scratch/repo/input/images/comparison-argo/vs-condition-category-condition-category000
/scratch/repo/input/images/comparison-argo/vs-device-kind-device-kind000
/scratch/repo/input/images/comparison-argo/vs-formatcodes-v3-HL7FormatCodes000
/scratch/repo/input/images/comparison-argo/vs-languages-Languages000
/scratch/repo/input/images/comparison-argo/vs-medication-codes-2.16.840.1.113762.1.4.1010.4000
/scratch/repo/input/images/comparison-argo/vs-narrative-status-us-core-narrative-status000
/scratch/repo/input/images/comparison-argo/vs-observation-ccdavitalsignresult-2.16.840.1.113883.3.88.12.80.62000
/scratch/repo/input/images/comparison-argo/vs-observation-codes-2.16.840.1.113762.1.4.1267.6000
/scratch/repo/input/images/comparison-argo/vs-observation-codes-us-core-laboratory-test-codes000
/scratch/repo/input/images/comparison-argo/vs-observation-status-us-core-observation-smoking-status-status000
/scratch/repo/input/images/comparison-argo/vs-procedure-type-us-core-procedure-code000
/scratch/repo/input/images/comparison-argo/vs-report-codes-us-core-diagnosticreport-report-and-note-codes000
/scratch/repo/input/images/comparison-argo/vs-report-codes-us-core-laboratory-test-codes000
/scratch/repo/input/images/comparison-argo/vs-vacc-status-immunization-status000
/scratch/repo/input/images/comparison-argo/warning000
/scratch/repo/input/images/comparison-argo/workflow000
/scratch/repo/input/images/comparison-argo/xver-paths-1.0000
/scratch/repo/input/images/comparison-argo/xver-paths-1.4000
/scratch/repo/input/images/comparison-argo/xver-paths-3.0000
/scratch/repo/input/images/comparison-argo/xver-paths-4.0000
/scratch/repo/input/images/comparison-argo/xver-paths-5.0000
/scratch/repo/input/images/comparison-argo/xver-paths-r2000
/scratch/repo/input/images/cross_red_circle.svg000
/scratch/repo/input/images/diagnostic-imaging000
/scratch/repo/input/images/encounter000
/scratch/repo/input/images/facility-information000
/scratch/repo/input/images/fhir-write1000
/scratch/repo/input/images/fhir-write2000
/scratch/repo/input/images/goals-and-preferences000
/scratch/repo/input/images/green_checkmark.svg000
/scratch/repo/input/images/health-insurance-information000
/scratch/repo/input/images/health-status-assessments000
/scratch/repo/input/images/immunizations000
/scratch/repo/input/images/includelines000
/scratch/repo/input/images/laboratory000
/scratch/repo/input/images/medical-devices000
/scratch/repo/input/images/medications000
/scratch/repo/input/images/minus_symbol.svg000
/scratch/repo/input/images/modifier-element-view000
/scratch/repo/input/images/observation000
/scratch/repo/input/images/orange_checkmark.svg000
/scratch/repo/input/images/orders000
/scratch/repo/input/images/org_logo000
/scratch/repo/input/images/org_logo_hl7000
/scratch/repo/input/images/patient-demographics000
/scratch/repo/input/images/patient-summary-and-plan000
/scratch/repo/input/images/problems000
/scratch/repo/input/images/procedures000
/scratch/repo/input/images/provenance000
/scratch/repo/input/images/relationships000
/scratch/repo/input/images/screening_and_assessments000
/scratch/repo/input/images/sdoh_condition000
/scratch/repo/input/images/tables000
/scratch/repo/input/images/tables/additional-uscdi-requirements000
/scratch/repo/input/images/tables/additional-uscdi-requirements000
/scratch/repo/input/images/tables/addl_uscdi_choice_refs000
/scratch/repo/input/images/tables/addl_uscdi_choice_refs000
/scratch/repo/input/images/tables/addl_uscdi_refs000
/scratch/repo/input/images/tables/addl_uscdi_refs000
/scratch/repo/input/images/tables/assessments-valuesets000
/scratch/repo/input/images/tables/assessments-valuesets000
/scratch/repo/input/images/tables/codesystem-ref-all-list000
/scratch/repo/input/images/tables/codesystem-ref-all-list000
/scratch/repo/input/images/tables/dstu2-r4-table000
/scratch/repo/input/images/tables/dstu2-r4-table000
/scratch/repo/input/images/tables/ms_choice_refs000
/scratch/repo/input/images/tables/ms_choice_refs000
/scratch/repo/input/images/tables/ms_refs000
/scratch/repo/input/images/tables/ms_refs000
/scratch/repo/input/images/tables/provenance-elements000
/scratch/repo/input/images/tables/provenance-elements000
/scratch/repo/input/images/tables/scopes000
/scratch/repo/input/images/tables/scopes000
/scratch/repo/input/images/tables/uscdi-table000
/scratch/repo/input/images/tables/uscdi-table000
/scratch/repo/input/images/tables/uscore-sps000
/scratch/repo/input/images/tables/uscore-sps000
/scratch/repo/input/images/tables/valueset-ref-all-list000
/scratch/repo/input/images/tables/valueset-ref-all-list000
/scratch/repo/input/images/tables/vsacname-fhiruri-map000
/scratch/repo/input/images/tables/vsacname-fhiruri-map000
/scratch/repo/input/images/todo000
/scratch/repo/input/images/uscore-observation-assessment-structure000
/scratch/repo/input/images/vital-signs000
/scratch/repo/input/images/vsac-1000
/scratch/repo/input/images/vsac-2000
/scratch/repo/input/images/vsac-3000
/scratch/repo/input/images/yearly-updates000
/scratch/repo/input/images/yellow_checkmark.svg000
/scratch/repo/input/includes/DAR-exception000
/scratch/repo/input/includes/SDOH_search_transaction000
/scratch/repo/input/includes/ValueSet-expansion-note000
/scratch/repo/input/includes/additional-codings000
/scratch/repo/input/includes/additional-requirements-intro000
/scratch/repo/input/includes/additional-uscdi-tabler000
/scratch/repo/input/includes/assessment-category-table-generator000
/scratch/repo/input/includes/assessment-valueset-table-generator000
/scratch/repo/input/includes/assessment_examples000
/scratch/repo/input/includes/boilerplate-clia-warning000
/scratch/repo/input/includes/ccds_table000
/scratch/repo/input/includes/codesystem-ref-all-table-generator000
/scratch/repo/input/includes/condition-quickstart000
/scratch/repo/input/includes/conditional-goals-guidance000
/scratch/repo/input/includes/conform-patient000
/scratch/repo/input/includes/diagnosticreport-clinical-note-post000
/scratch/repo/input/includes/diagnosticreport-quickstart000
/scratch/repo/input/includes/diff-display-note000
/scratch/repo/input/includes/docref000
/scratch/repo/input/includes/docref-example1000
/scratch/repo/input/includes/docref-example2000
/scratch/repo/input/includes/documentreference-clinical-note-post000
/scratch/repo/input/includes/documentreference-quickstart000
/scratch/repo/input/includes/dstu2-r4-table2000
/scratch/repo/input/includes/encounter-location000
/scratch/repo/input/includes/example-list-generator000
/scratch/repo/input/includes/example_link000
/scratch/repo/input/includes/examplebutton000
/scratch/repo/input/includes/examplebutton_default000
/scratch/repo/input/includes/ext-list-generator000
/scratch/repo/input/includes/get-all-active-meds000
/scratch/repo/input/includes/get-all-active-meds-searchbundle000
/scratch/repo/input/includes/get-all-allergy-provenance-future-health000
/scratch/repo/input/includes/get-all-allergy-provenance-good-health000
/scratch/repo/input/includes/get-all-allergy-provenance-sunshine-health000
/scratch/repo/input/includes/get-all-ecounter-meds-searchbundle000
/scratch/repo/input/includes/get-all-enc-meds000
/scratch/repo/input/includes/get-all-meds000
/scratch/repo/input/includes/get-all-meds-searchbundle000
/scratch/repo/input/includes/granular-scopes-table000
/scratch/repo/input/includes/img000
/scratch/repo/input/includes/img-med000
/scratch/repo/input/includes/img-narrow000
/scratch/repo/input/includes/img-portrait000
/scratch/repo/input/includes/img-portrait-med000
/scratch/repo/input/includes/img-small000
/scratch/repo/input/includes/link-list000
/scratch/repo/input/includes/logo000
/scratch/repo/input/includes/mcc-valueset-list-generator000
/scratch/repo/input/includes/missing-status000
/scratch/repo/input/includes/ms-target-table-generator000
/scratch/repo/input/includes/new_page000
/scratch/repo/input/includes/non-uscdi-profiles000
/scratch/repo/input/includes/nonnormative-example-boilerplate000
/scratch/repo/input/includes/note-and-report-types-scenario1000
/scratch/repo/input/includes/note-and-report-types-scenario2000
/scratch/repo/input/includes/note-and-report-types-scenario3000
/scratch/repo/input/includes/note-and-report-types-scenario4000
/scratch/repo/input/includes/obs_cat_guidance000
/scratch/repo/input/includes/observation-quickstart1000
/scratch/repo/input/includes/observation_guidance_1000
/scratch/repo/input/includes/page-link-list000
/scratch/repo/input/includes/prov-white-list000
/scratch/repo/input/includes/provenance-author-bullet-generator000
/scratch/repo/input/includes/provenance-source-table-generator000
/scratch/repo/input/includes/questionnaireresponse-context-note000
/scratch/repo/input/includes/quickstart-intro000
/scratch/repo/input/includes/r4-link-list000
/scratch/repo/input/includes/read-and-write-format-scenario1000
/scratch/repo/input/includes/read-and-write-format-scenario2000
/scratch/repo/input/includes/representing-meds000
/scratch/repo/input/includes/res-list-generator000
/scratch/repo/input/includes/resource-scopes-table000
/scratch/repo/input/includes/schematron-list-generator000
/scratch/repo/input/includes/sd-list-generator000
/scratch/repo/input/includes/sd_link000
/scratch/repo/input/includes/should-project-us000
/scratch/repo/input/includes/specimen-include-note000
/scratch/repo/input/includes/uscdi-uscore-map000
/scratch/repo/input/includes/uscdi-uscore-version-table000
/scratch/repo/input/includes/uscore_sp_list000
/scratch/repo/input/includes/valueset-ref-all-table-generator000
/scratch/repo/input/includes/vitals-guidance000
/scratch/repo/input/includes/whats-new/v8000
/scratch/repo/input/includes/whats-new/v8-ballot000
/scratch/repo/input/includes/whats-new/v8.0.1000
/scratch/repo/input/includes/write-and-docref000
/scratch/repo/input/intro-notes000
/scratch/repo/input/intro-notes/DiagnosticReport-cbc-intro000
/scratch/repo/input/intro-notes/DiagnosticReport-cbc-intro000
/scratch/repo/input/intro-notes/DiagnosticReport-metabolic-panel-intro000
/scratch/repo/input/intro-notes/DiagnosticReport-metabolic-panel-intro000
/scratch/repo/input/intro-notes/Observation-cbc-erythrocytes-intro000
/scratch/repo/input/intro-notes/Observation-cbc-erythrocytes-intro000
/scratch/repo/input/intro-notes/Observation-cbc-hematocrit-intro000
/scratch/repo/input/intro-notes/Observation-cbc-hematocrit-intro000
/scratch/repo/input/intro-notes/Observation-cbc-hemoglobin-intro000
/scratch/repo/input/intro-notes/Observation-cbc-hemoglobin-intro000
/scratch/repo/input/intro-notes/Observation-cbc-leukocytes-intro000
/scratch/repo/input/intro-notes/Observation-cbc-leukocytes-intro000
/scratch/repo/input/intro-notes/Observation-cbc-mch-intro000
/scratch/repo/input/intro-notes/Observation-cbc-mch-intro000
/scratch/repo/input/intro-notes/Observation-cbc-mchc-intro000
/scratch/repo/input/intro-notes/Observation-cbc-mchc-intro000
/scratch/repo/input/intro-notes/Observation-cbc-mcv-intro000
/scratch/repo/input/intro-notes/Observation-cbc-mcv-intro000
/scratch/repo/input/intro-notes/Observation-cbc-platelets-intro000
/scratch/repo/input/intro-notes/Observation-cbc-platelets-intro000
/scratch/repo/input/intro-notes/Observation-serum-bun-intro000
/scratch/repo/input/intro-notes/Observation-serum-bun-intro000
/scratch/repo/input/intro-notes/Observation-serum-calcium-intro000
/scratch/repo/input/intro-notes/Observation-serum-calcium-intro000
/scratch/repo/input/intro-notes/Observation-serum-chloride-intro000
/scratch/repo/input/intro-notes/Observation-serum-chloride-intro000
/scratch/repo/input/intro-notes/Observation-serum-co2-intro000
/scratch/repo/input/intro-notes/Observation-serum-co2-intro000
/scratch/repo/input/intro-notes/Observation-serum-creatinine-intro000
/scratch/repo/input/intro-notes/Observation-serum-creatinine-intro000
/scratch/repo/input/intro-notes/Observation-serum-glucose-intro000
/scratch/repo/input/intro-notes/Observation-serum-glucose-intro000
/scratch/repo/input/intro-notes/Observation-serum-potassium-intro000
/scratch/repo/input/intro-notes/Observation-serum-potassium-intro000
/scratch/repo/input/intro-notes/Observation-serum-sodium-intro000
/scratch/repo/input/intro-notes/Observation-serum-sodium-intro000
/scratch/repo/input/intro-notes/StructureDefinition-head-occipital-frontal-circumference-percentile-intro000
/scratch/repo/input/intro-notes/StructureDefinition-head-occipital-frontal-circumference-percentile-intro000
/scratch/repo/input/intro-notes/StructureDefinition-head-occipital-frontal-circumference-percentile-notes000
/scratch/repo/input/intro-notes/StructureDefinition-head-occipital-frontal-circumference-percentile-notes000
/scratch/repo/input/intro-notes/StructureDefinition-pediatric-bmi-for-age-intro000
/scratch/repo/input/intro-notes/StructureDefinition-pediatric-bmi-for-age-intro000
/scratch/repo/input/intro-notes/StructureDefinition-pediatric-bmi-for-age-notes000
/scratch/repo/input/intro-notes/StructureDefinition-pediatric-bmi-for-age-notes000
/scratch/repo/input/intro-notes/StructureDefinition-pediatric-weight-for-height-intro000
/scratch/repo/input/intro-notes/StructureDefinition-pediatric-weight-for-height-intro000
/scratch/repo/input/intro-notes/StructureDefinition-pediatric-weight-for-height-notes000
/scratch/repo/input/intro-notes/StructureDefinition-pediatric-weight-for-height-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-adi-documentreference-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-adi-documentreference-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-adi-documentreference-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-adi-documentreference-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-allergyintolerance-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-allergyintolerance-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-allergyintolerance-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-allergyintolerance-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-average-blood-pressure-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-average-blood-pressure-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-average-blood-pressure-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-average-blood-pressure-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-birthsex-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-birthsex-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-blood-pressure-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-blood-pressure-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-blood-pressure-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-blood-pressure-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-bmi-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-bmi-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-bmi-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-bmi-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-body-height-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-body-height-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-body-height-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-body-height-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-body-temperature-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-body-temperature-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-body-temperature-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-body-temperature-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-body-weight-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-body-weight-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-body-weight-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-body-weight-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-care-experience-preference-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-care-experience-preference-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-care-experience-preference-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-care-experience-preference-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-careplan-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-careplan-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-careplan-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-careplan-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-careteam-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-careteam-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-careteam-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-careteam-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-condition-encounter-diagnosis-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-condition-encounter-diagnosis-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-condition-encounter-diagnosis-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-condition-encounter-diagnosis-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-condition-problems-health-concerns-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-condition-problems-health-concerns-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-condition-problems-health-concerns-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-condition-problems-health-concerns-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-coverage-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-coverage-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-coverage-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-coverage-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-diagnosticreport-lab-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-diagnosticreport-lab-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-diagnosticreport-lab-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-diagnosticreport-lab-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-diagnosticreport-note-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-diagnosticreport-note-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-diagnosticreport-note-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-diagnosticreport-note-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-documentreference-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-documentreference-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-documentreference-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-documentreference-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-encounter-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-encounter-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-encounter-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-encounter-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-ethnicity-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-ethnicity-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-goal-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-goal-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-goal-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-goal-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-head-circumference-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-head-circumference-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-head-circumference-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-head-circumference-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-heart-rate-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-heart-rate-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-heart-rate-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-heart-rate-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-immunization-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-immunization-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-immunization-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-immunization-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-implantable-device-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-implantable-device-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-implantable-device-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-implantable-device-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-location-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-location-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-location-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-location-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-medication-adherence-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-medication-adherence-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-medication-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-medication-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-medication-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-medication-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-medicationdispense-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-medicationdispense-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-medicationdispense-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-medicationdispense-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-medicationrequest-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-medicationrequest-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-medicationrequest-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-medicationrequest-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-adi-documentation-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-adi-documentation-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-adi-documentation-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-adi-documentation-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-clinical-result-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-clinical-result-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-clinical-result-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-clinical-result-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-lab-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-lab-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-lab-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-lab-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-occupation-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-occupation-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-occupation-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-occupation-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-pregnancyintent-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-pregnancyintent-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-pregnancyintent-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-pregnancyintent-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-pregnancystatus-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-pregnancystatus-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-pregnancystatus-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-pregnancystatus-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-screening-assessment-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-screening-assessment-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-screening-assessment-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-screening-assessment-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-sexual-orientation-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-sexual-orientation-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-sexual-orientation-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-observation-sexual-orientation-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-organization-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-organization-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-organization-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-organization-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-patient-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-patient-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-patient-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-patient-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-practitioner-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-practitioner-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-practitioner-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-practitioner-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-practitionerrole-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-practitionerrole-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-practitionerrole-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-practitionerrole-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-procedure-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-procedure-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-procedure-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-procedure-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-provenance-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-provenance-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-provenance-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-provenance-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-pulse-oximetry-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-pulse-oximetry-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-pulse-oximetry-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-pulse-oximetry-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-questionnaireresponse-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-questionnaireresponse-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-questionnaireresponse-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-questionnaireresponse-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-race-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-race-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-relatedperson-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-relatedperson-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-relatedperson-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-relatedperson-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-respiratory-rate-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-respiratory-rate-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-respiratory-rate-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-respiratory-rate-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-servicerequest-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-servicerequest-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-servicerequest-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-servicerequest-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-sex-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-sex-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-simple-observation-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-simple-observation-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-simple-observation-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-simple-observation-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-smokingstatus-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-smokingstatus-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-smokingstatus-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-smokingstatus-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-specimen-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-specimen-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-specimen-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-specimen-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-treatment-intervention-preference-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-treatment-intervention-preference-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-treatment-intervention-preference-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-treatment-intervention-preference-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-tribal-affiliation-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-tribal-affiliation-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-vital-signs-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-vital-signs-intro000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-vital-signs-notes000
/scratch/repo/input/intro-notes/StructureDefinition-us-core-vital-signs-notes000
/scratch/repo/input/intro-notes/ValueSet-detailed-ethnicity-intro000
/scratch/repo/input/intro-notes/ValueSet-detailed-ethnicity-intro000
/scratch/repo/input/intro-notes/ValueSet-detailed-race-intro000
/scratch/repo/input/intro-notes/ValueSet-detailed-race-intro000
/scratch/repo/input/intro-notes/ValueSet-simple-language-intro000
/scratch/repo/input/intro-notes/ValueSet-simple-language-intro000
/scratch/repo/input/intro-notes/ValueSet-us-core-location-type-intro000
/scratch/repo/input/intro-notes/ValueSet-us-core-location-type-intro000
/scratch/repo/input/intro-notes/ValueSet-us-core-pregnancy-intent-intro000
/scratch/repo/input/intro-notes/ValueSet-us-core-pregnancy-intent-intro000
/scratch/repo/input/pagecontent000
/scratch/repo/input/pagecontent/ImplementationGuide-hl7.fhir.us.core000
/scratch/repo/input/pagecontent/ImplementationGuide-hl7.fhir.us.core000
/scratch/repo/input/pagecontent/basic-provenance000
/scratch/repo/input/pagecontent/basic-provenance000
/scratch/repo/input/pagecontent/capability-statements000
/scratch/repo/input/pagecontent/capability-statements000
/scratch/repo/input/pagecontent/changes000
/scratch/repo/input/pagecontent/changes000
/scratch/repo/input/pagecontent/changes-between-versions000
/scratch/repo/input/pagecontent/changes-between-versions000
/scratch/repo/input/pagecontent/clinical-notes000
/scratch/repo/input/pagecontent/clinical-notes000
/scratch/repo/input/pagecontent/conformance000
/scratch/repo/input/pagecontent/conformance000
/scratch/repo/input/pagecontent/downloads000
/scratch/repo/input/pagecontent/downloads000
/scratch/repo/input/pagecontent/element-level-provenance000
/scratch/repo/input/pagecontent/element-level-provenance000
/scratch/repo/input/pagecontent/examples000
/scratch/repo/input/pagecontent/examples000
/scratch/repo/input/pagecontent/general-guidance000
/scratch/repo/input/pagecontent/general-guidance000
/scratch/repo/input/pagecontent/general-requirements000
/scratch/repo/input/pagecontent/general-requirements000
/scratch/repo/input/pagecontent/guidance000
/scratch/repo/input/pagecontent/guidance000
/scratch/repo/input/pagecontent/index000
/scratch/repo/input/pagecontent/index000
/scratch/repo/input/pagecontent/looking-ahead000
/scratch/repo/input/pagecontent/looking-ahead000
/scratch/repo/input/pagecontent/medication-list000
/scratch/repo/input/pagecontent/medication-list000
/scratch/repo/input/pagecontent/must-support000
/scratch/repo/input/pagecontent/must-support000
/scratch/repo/input/pagecontent/observation-summary000
/scratch/repo/input/pagecontent/observation-summary000
/scratch/repo/input/pagecontent/patient-data-feed000
/scratch/repo/input/pagecontent/patient-data-feed000
/scratch/repo/input/pagecontent/patient-data-feed-additional-resources000
/scratch/repo/input/pagecontent/patient-data-feed-additional-resources000
/scratch/repo/input/pagecontent/profiles-and-extensions000
/scratch/repo/input/pagecontent/profiles-and-extensions000
/scratch/repo/input/pagecontent/relationship-with-other-igs000
/scratch/repo/input/pagecontent/relationship-with-other-igs000
/scratch/repo/input/pagecontent/scopes000
/scratch/repo/input/pagecontent/scopes000
/scratch/repo/input/pagecontent/screening-and-assessments000
/scratch/repo/input/pagecontent/screening-and-assessments000
/scratch/repo/input/pagecontent/search-parameters-and-operations000
/scratch/repo/input/pagecontent/search-parameters-and-operations000
/scratch/repo/input/pagecontent/security000
/scratch/repo/input/pagecontent/security000
/scratch/repo/input/pagecontent/terminology000
/scratch/repo/input/pagecontent/terminology000
/scratch/repo/input/pagecontent/us-core-roadmap000
/scratch/repo/input/pagecontent/us-core-roadmap000
/scratch/repo/input/pagecontent/uscdi000
/scratch/repo/input/pagecontent/uscdi000
/scratch/repo/input/pagecontent/vsacname-fhiruri-map000
/scratch/repo/input/pagecontent/vsacname-fhiruri-map000
/scratch/repo/input/pagecontent/writing-vital-signs000
/scratch/repo/input/pagecontent/writing-vital-signs000
/scratch/repo/input/resources/CodeSystem-careplan-category000
/scratch/repo/input/resources/CodeSystem-condition-category000
/scratch/repo/input/resources/CodeSystem-us-core-category000
/scratch/repo/input/resources/CodeSystem-us-core-documentreference-category000
/scratch/repo/input/resources/CodeSystem-us-core-provenance-participant-type000
/scratch/repo/input/resources/StructureDefinition-pediatric-bmi-for-age000
/scratch/repo/input/resources/StructureDefinition-pediatric-weight-for-height000
/scratch/repo/input/resources/StructureDefinition-us-core-adi-documentreference000
/scratch/repo/input/resources/StructureDefinition-us-core-allergyintolerance000
/scratch/repo/input/resources/StructureDefinition-us-core-authentication-time000
/scratch/repo/input/resources/StructureDefinition-us-core-average-blood-pressure000
/scratch/repo/input/resources/StructureDefinition-us-core-birthsex000
/scratch/repo/input/resources/StructureDefinition-us-core-blood-pressure000
/scratch/repo/input/resources/StructureDefinition-us-core-bmi000
/scratch/repo/input/resources/StructureDefinition-us-core-body-height000
/scratch/repo/input/resources/StructureDefinition-us-core-body-temperature000
/scratch/repo/input/resources/StructureDefinition-us-core-body-weight000
/scratch/repo/input/resources/StructureDefinition-us-core-care-experience-preference000
/scratch/repo/input/resources/StructureDefinition-us-core-careplan000
/scratch/repo/input/resources/StructureDefinition-us-core-careteam000
/scratch/repo/input/resources/StructureDefinition-us-core-condition-encounter-diagnosis000
/scratch/repo/input/resources/StructureDefinition-us-core-condition-problems-health-concerns020
/scratch/repo/input/resources/StructureDefinition-us-core-coverage000
/scratch/repo/input/resources/StructureDefinition-us-core-diagnosticreport-lab000
/scratch/repo/input/resources/StructureDefinition-us-core-diagnosticreport-note000
/scratch/repo/input/resources/StructureDefinition-us-core-direct000
/scratch/repo/input/resources/StructureDefinition-us-core-documentreference000
/scratch/repo/input/resources/StructureDefinition-us-core-encounter030
/scratch/repo/input/resources/StructureDefinition-us-core-ethnicity000
/scratch/repo/input/resources/StructureDefinition-us-core-extension-questionnaire-uri000
/scratch/repo/input/resources/StructureDefinition-us-core-genderIdentity000
/scratch/repo/input/resources/StructureDefinition-us-core-goal000
/scratch/repo/input/resources/StructureDefinition-us-core-head-circumference000
/scratch/repo/input/resources/StructureDefinition-us-core-heart-rate000
/scratch/repo/input/resources/StructureDefinition-us-core-immunization000
/scratch/repo/input/resources/StructureDefinition-us-core-implantable-device000
/scratch/repo/input/resources/StructureDefinition-us-core-individual-sex000
/scratch/repo/input/resources/StructureDefinition-us-core-interpreter-needed000
/scratch/repo/input/resources/StructureDefinition-us-core-jurisdiction000
/scratch/repo/input/resources/StructureDefinition-us-core-location010
/scratch/repo/input/resources/StructureDefinition-us-core-medication000
/scratch/repo/input/resources/StructureDefinition-us-core-medication-adherence000
/scratch/repo/input/resources/StructureDefinition-us-core-medicationdispense000
/scratch/repo/input/resources/StructureDefinition-us-core-medicationrequest000
/scratch/repo/input/resources/StructureDefinition-us-core-observation-adi-documentation020
/scratch/repo/input/resources/StructureDefinition-us-core-observation-clinical-result000
/scratch/repo/input/resources/StructureDefinition-us-core-observation-lab000
/scratch/repo/input/resources/StructureDefinition-us-core-observation-occupation000
/scratch/repo/input/resources/StructureDefinition-us-core-observation-pregnancyintent000
/scratch/repo/input/resources/StructureDefinition-us-core-observation-pregnancystatus000
/scratch/repo/input/resources/StructureDefinition-us-core-observation-screening-assessment000
/scratch/repo/input/resources/StructureDefinition-us-core-observation-sexual-orientation000
/scratch/repo/input/resources/StructureDefinition-us-core-organization000
/scratch/repo/input/resources/StructureDefinition-us-core-practitioner000
/scratch/repo/input/resources/StructureDefinition-us-core-practitionerrole000
/scratch/repo/input/resources/StructureDefinition-us-core-procedure000
/scratch/repo/input/resources/StructureDefinition-us-core-provenance010
/scratch/repo/input/resources/StructureDefinition-us-core-pulse-oximetry000
/scratch/repo/input/resources/StructureDefinition-us-core-questionnaireresponse040
/scratch/repo/input/resources/StructureDefinition-us-core-race000
/scratch/repo/input/resources/StructureDefinition-us-core-relatedperson000
/scratch/repo/input/resources/StructureDefinition-us-core-respiratory-rate000
/scratch/repo/input/resources/StructureDefinition-us-core-sex000
/scratch/repo/input/resources/StructureDefinition-us-core-simple-observation000
/scratch/repo/input/resources/StructureDefinition-us-core-smokingstatus000
/scratch/repo/input/resources/StructureDefinition-us-core-specimen020
/scratch/repo/input/resources/StructureDefinition-us-core-treatment-intervention-preference000
/scratch/repo/input/resources/StructureDefinition-us-core-tribal-affiliation000
/scratch/repo/input/resources/StructureDefinition-us-core-uscdi-requirements000
/scratch/repo/input/resources/StructureDefinition-us-core-vital-signs000
/scratch/repo/input/resources/ValueSet-us-core-clinical-note-type000
/scratch/repo/input/resources/ValueSet-us-core-clinical-result-observation-category001
/scratch/repo/input/resources/ValueSet-us-core-condition-code-current000
/scratch/repo/input/resources/ValueSet-us-core-diagnosticreport-category000
/scratch/repo/input/resources/ValueSet-us-core-diagnosticreport-report-and-note-codes000
/scratch/repo/input/resources/ValueSet-us-core-documentreference-category000
/scratch/repo/input/resources/ValueSet-us-core-documentreference-type001
/scratch/repo/input/resources/ValueSet-us-core-narrative-status000
/scratch/repo/input/resources/ValueSet-us-core-observation-smoking-status-status000
/scratch/repo/input/resources/ValueSet-us-core-provenance-participant-type001
/scratch/repo/input/resources/ValueSet-us-core-screening-assessment-condition-category000
/scratch/repo/input/resources/ValueSet-us-core-screening-assessment-observation-category001
/scratch/repo/input/resources/ValueSet-us-core-screening-assessment-observation-maximum-category011
/scratch/repo/input/resources/ValueSet-us-core-simple-observation-category001
/scratch/repo/input/resources/ValueSet-us-core-specimen-condition010
/scratch/repo/input/resources/capabilitystatement-us-core-client000
/scratch/repo/input/resources/capabilitystatement-us-core-server000
/scratch/repo/input/resources/operationdefinition-docref000
/scratch/repo/input/resources/searchparameter-us-core-allergyintolerance-clinical-status000
/scratch/repo/input/resources/searchparameter-us-core-allergyintolerance-patient000
/scratch/repo/input/resources/searchparameter-us-core-careplan-category000
/scratch/repo/input/resources/searchparameter-us-core-careplan-date000
/scratch/repo/input/resources/searchparameter-us-core-careplan-patient000
/scratch/repo/input/resources/searchparameter-us-core-careplan-status000
/scratch/repo/input/resources/searchparameter-us-core-careteam-patient000
/scratch/repo/input/resources/searchparameter-us-core-careteam-role000
/scratch/repo/input/resources/searchparameter-us-core-careteam-status000
/scratch/repo/input/resources/searchparameter-us-core-condition-abatement-date000
/scratch/repo/input/resources/searchparameter-us-core-condition-asserted-date000
/scratch/repo/input/resources/searchparameter-us-core-condition-category000
/scratch/repo/input/resources/searchparameter-us-core-condition-clinical-status000
/scratch/repo/input/resources/searchparameter-us-core-condition-code000
/scratch/repo/input/resources/searchparameter-us-core-condition-encounter000
/scratch/repo/input/resources/searchparameter-us-core-condition-lastUpdated000
/scratch/repo/input/resources/searchparameter-us-core-condition-onset-date000
/scratch/repo/input/resources/searchparameter-us-core-condition-patient000
/scratch/repo/input/resources/searchparameter-us-core-condition-recorded-date000
/scratch/repo/input/resources/searchparameter-us-core-coverage-patient000
/scratch/repo/input/resources/searchparameter-us-core-device-patient000
/scratch/repo/input/resources/searchparameter-us-core-device-status000
/scratch/repo/input/resources/searchparameter-us-core-device-type000
/scratch/repo/input/resources/searchparameter-us-core-diagnosticreport-category000
/scratch/repo/input/resources/searchparameter-us-core-diagnosticreport-code000
/scratch/repo/input/resources/searchparameter-us-core-diagnosticreport-date000
/scratch/repo/input/resources/searchparameter-us-core-diagnosticreport-lastUpdated000
/scratch/repo/input/resources/searchparameter-us-core-diagnosticreport-patient000
/scratch/repo/input/resources/searchparameter-us-core-diagnosticreport-status000
/scratch/repo/input/resources/searchparameter-us-core-documentreference-category000
/scratch/repo/input/resources/searchparameter-us-core-documentreference-date000
/scratch/repo/input/resources/searchparameter-us-core-documentreference-id000
/scratch/repo/input/resources/searchparameter-us-core-documentreference-patient000
/scratch/repo/input/resources/searchparameter-us-core-documentreference-period000
/scratch/repo/input/resources/searchparameter-us-core-documentreference-status000
/scratch/repo/input/resources/searchparameter-us-core-documentreference-type000
/scratch/repo/input/resources/searchparameter-us-core-encounter-class000
/scratch/repo/input/resources/searchparameter-us-core-encounter-date000
/scratch/repo/input/resources/searchparameter-us-core-encounter-discharge-disposition000
/scratch/repo/input/resources/searchparameter-us-core-encounter-id000
/scratch/repo/input/resources/searchparameter-us-core-encounter-identifier000
/scratch/repo/input/resources/searchparameter-us-core-encounter-lastUpdated000
/scratch/repo/input/resources/searchparameter-us-core-encounter-location000
/scratch/repo/input/resources/searchparameter-us-core-encounter-patient000
/scratch/repo/input/resources/searchparameter-us-core-encounter-status000
/scratch/repo/input/resources/searchparameter-us-core-encounter-type000
/scratch/repo/input/resources/searchparameter-us-core-ethnicity000
/scratch/repo/input/resources/searchparameter-us-core-goal-description000
/scratch/repo/input/resources/searchparameter-us-core-goal-lifecycle-status000
/scratch/repo/input/resources/searchparameter-us-core-goal-patient000
/scratch/repo/input/resources/searchparameter-us-core-goal-target-date000
/scratch/repo/input/resources/searchparameter-us-core-immunization-date000
/scratch/repo/input/resources/searchparameter-us-core-immunization-patient000
/scratch/repo/input/resources/searchparameter-us-core-immunization-status000
/scratch/repo/input/resources/searchparameter-us-core-location-address000
/scratch/repo/input/resources/searchparameter-us-core-location-address-city000
/scratch/repo/input/resources/searchparameter-us-core-location-address-postalcode000
/scratch/repo/input/resources/searchparameter-us-core-location-address-state000
/scratch/repo/input/resources/searchparameter-us-core-location-name000
/scratch/repo/input/resources/searchparameter-us-core-medicationdispense-patient000
/scratch/repo/input/resources/searchparameter-us-core-medicationdispense-status000
/scratch/repo/input/resources/searchparameter-us-core-medicationdispense-type000
/scratch/repo/input/resources/searchparameter-us-core-medicationrequest-authoredon000
/scratch/repo/input/resources/searchparameter-us-core-medicationrequest-encounter000
/scratch/repo/input/resources/searchparameter-us-core-medicationrequest-intent000
/scratch/repo/input/resources/searchparameter-us-core-medicationrequest-patient000
/scratch/repo/input/resources/searchparameter-us-core-medicationrequest-status000
/scratch/repo/input/resources/searchparameter-us-core-observation-category000
/scratch/repo/input/resources/searchparameter-us-core-observation-code000
/scratch/repo/input/resources/searchparameter-us-core-observation-date000
/scratch/repo/input/resources/searchparameter-us-core-observation-lastUpdated000
/scratch/repo/input/resources/searchparameter-us-core-observation-patient000
/scratch/repo/input/resources/searchparameter-us-core-observation-status000
/scratch/repo/input/resources/searchparameter-us-core-organization-address000
/scratch/repo/input/resources/searchparameter-us-core-organization-name000
/scratch/repo/input/resources/searchparameter-us-core-patient-birthdate000
/scratch/repo/input/resources/searchparameter-us-core-patient-death-date000
/scratch/repo/input/resources/searchparameter-us-core-patient-family000
/scratch/repo/input/resources/searchparameter-us-core-patient-given000
/scratch/repo/input/resources/searchparameter-us-core-patient-id000
/scratch/repo/input/resources/searchparameter-us-core-patient-identifier000
/scratch/repo/input/resources/searchparameter-us-core-patient-name000
/scratch/repo/input/resources/searchparameter-us-core-practitioner-id000
/scratch/repo/input/resources/searchparameter-us-core-practitioner-identifier000
/scratch/repo/input/resources/searchparameter-us-core-practitioner-name000
/scratch/repo/input/resources/searchparameter-us-core-practitionerrole-practitioner000
/scratch/repo/input/resources/searchparameter-us-core-practitionerrole-specialty000
/scratch/repo/input/resources/searchparameter-us-core-procedure-code000
/scratch/repo/input/resources/searchparameter-us-core-procedure-date000
/scratch/repo/input/resources/searchparameter-us-core-procedure-patient000
/scratch/repo/input/resources/searchparameter-us-core-procedure-status000
/scratch/repo/input/resources/searchparameter-us-core-questionnaireresponse-authored000
/scratch/repo/input/resources/searchparameter-us-core-questionnaireresponse-id000
/scratch/repo/input/resources/searchparameter-us-core-questionnaireresponse-patient000
/scratch/repo/input/resources/searchparameter-us-core-questionnaireresponse-questionnaire000
/scratch/repo/input/resources/searchparameter-us-core-questionnaireresponse-status000
/scratch/repo/input/resources/searchparameter-us-core-race000
/scratch/repo/input/resources/searchparameter-us-core-relatedperson-id000
/scratch/repo/input/resources/searchparameter-us-core-relatedperson-name000
/scratch/repo/input/resources/searchparameter-us-core-relatedperson-patient000
/scratch/repo/input/resources/searchparameter-us-core-servicerequest-authored000
/scratch/repo/input/resources/searchparameter-us-core-servicerequest-category000
/scratch/repo/input/resources/searchparameter-us-core-servicerequest-code000
/scratch/repo/input/resources/searchparameter-us-core-servicerequest-id000
/scratch/repo/input/resources/searchparameter-us-core-servicerequest-patient000
/scratch/repo/input/resources/searchparameter-us-core-servicerequest-status000
/scratch/repo/input/resources/searchparameter-us-core-specimen-id000
/scratch/repo/input/resources/searchparameter-us-core-specimen-patient000
/scratch/repo/input/resources/structuredefinition-head-occipital-frontal-circumference-percentile000
/scratch/repo/input/resources/structuredefinition-us-core-patient000
/scratch/repo/input/resources/structuredefinition-us-core-servicerequest000
/scratch/repo/input/resources/valueset-us-core-condition-code000
/scratch/repo/input/resources/valueset-us-core-goal-description010
/scratch/repo/input/resources/valueset-us-core-laboratory-test-codes000
/scratch/repo/input/resources/valueset-us-core-problem-or-health-concern001
/scratch/repo/input/resources/valueset-us-core-procedure-code010
/scratch/repo/input/resources/valueset-us-core-servicerequest-category000
/scratch/repo/temp/pages/_includes/artifacts000
/scratch/repo/template/config000
/scratch/repo/template/config/_config000

n/a Show Validation Information

warningThe jira specification file appears to be out of date with the versions, artifacts and pages currently defined in the IG. A proposed revised file to be reviewed and, if appropriate, submitted as a pull request against the XML folder in https://github.com/HL7/JIRA-Spec-Artifacts. To see the differences, perform a file compare on 'template/jira-current.xml' (a normalized view of what is in Github) and 'template/jira-new.xml' (reflects current IG content)
CapabilityStatement-us-core-client.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: '' CONFORMANCE_STATEMENT_WORD
CapabilityStatement-us-core-server.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: '' CONFORMANCE_STATEMENT_WORD
OperationDefinition-docref.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' This operation is used to return all the references to documents related to a patient. It is invoked on a FHIR Server's DocumentReference endpoint (e.g., [base]/DocumentReference/$docref) and operates across all DocumentReference instances. The operation requires a patient id and takes the optional input parameters: start date end date document type on-demand profile and returns a searchset Bundle containing DocumentReference resources for the patient. If the server has stored documents or can create documents for the patient and those documents are available for the user, the server returns the DocumentReference resources associated with documents. This operation's intended use is to provide a way for providers or patients to access their available documents. The document itself can be subsequently retrieved using the link provided in the DocumentReference.content.attachment.url element. The link could be a FHIR endpoint to a Binary Resource or some other document repository. This operation is different from a FHIR RESTful query on DocumentReference by patient and type and date range because: It is used to request a server to generate a document based on the specified parameters. If no parameters are specified, the server SHALL return a DocumentReference to the patient's current C-CDA CCD. If the server cannot generate a document based on the specified parameters, the operation will return an empty search bundle. Unless the client indicates they are only interested in 'on-demand' documents using the on-demand parameter, the server SHOULD return DocumentReference instances for existing documents that meet the request parameters In this regard, this operation is similar to a FHIR RESTful query. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-allergyintolerance-clinical-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' active | inactive | resolved NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-allergyintolerance-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Who the sensitivity is for NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-careplan-category​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Type of plan NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-careplan-date​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Time period plan covers NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-careplan-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Who the care plan is for NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-careplan-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' draft | active | on-hold | revoked | completed | entered-in-error | unknown NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-careteam-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Who care team is for NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-careteam-role​.htmlinformationThe html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: ' multipleOr : True (Conformance Expectation = MAY)' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-careteam-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' proposed | active | suspended | inactive | entered-in-error NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-condition-abatement-date​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Date-related abatements (dateTime and period) NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-condition-asserted-date​.htmlinformationThe html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: ' multipleOr : True (Conformance Expectation = MAY)' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-condition-category​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The category of the condition NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-condition-clinical-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The clinical status of the condition NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-condition-code​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Code for the condition NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-condition-encounter​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Encounter created as part of NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-condition-lastupdated​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' When the resource version last changed NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-condition-onset-date​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Date related onsets (dateTime and Period) NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-condition-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Who has the condition? NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-condition-recorded-date​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Date record was first recorded NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-coverage-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Retrieve coverages for a patient NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-device-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Patient information, if the resource is affixed to a person NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-device-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' active | inactive | entered-in-error | unknown NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-device-type​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The type of the device NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-diagnosticreport-category​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Which diagnostic discipline/department created the report NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-diagnosticreport-code​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The code for the report, as opposed to codes for the atomic results, which are the names on the observation resource referred to from the result NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-diagnosticreport-date​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The clinically relevant time of the report NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-diagnosticreport-lastupdated​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' When the resource version last changed NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-diagnosticreport-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The subject of the report if a patient NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-diagnosticreport-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The status of the report NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-documentreference-category​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Categorization of document NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-documentreference-date​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' When this document reference was created NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-documentreference-id​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Logical id of this artifact NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-documentreference-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Who/what is the subject of the document NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-documentreference-period​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Time of service that is being documented NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-documentreference-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' current | superseded | entered-in-error NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-documentreference-type​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Kind of document (LOINC if possible) NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-encounter-class​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Classification of patient encounter NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-encounter-date​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' A date within the period the Encounter lasted NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-encounter-discharge-disposition​.htmlinformationThe html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: ' multipleOr : True (Conformance Expectation = MAY)' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-encounter-id​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Logical id of this artifact NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-encounter-identifier​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Identifier(s) by which this encounter is known NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-encounter-lastupdated​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' When the resource version last changed NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-encounter-location​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Location the encounter takes place NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-encounter-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The patient or group present at the encounter NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-encounter-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' planned | arrived | triaged | in-progress | onleave | finished | cancelled + NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-encounter-type​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Specific type of encounter NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-ethnicity.htmlinformationThe html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: ' multipleOr : True (Conformance Expectation = MAY)' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-goal-description​.htmlinformationThe html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: ' multipleOr : True (Conformance Expectation = MAY)' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-goal-lifecycle-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' proposed | planned | accepted | active | on-hold | completed | cancelled | entered-in-error | rejected NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-goal-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Who this goal is intended for NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-goal-target-date​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Reach goal on or before NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-immunization-date​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Vaccination (non)-Administration Date NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-immunization-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The patient for the vaccination record NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-immunization-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Immunization event status NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-location-address-city​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' A city specified in an address NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-location-address-postalcode​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' A postal code specified in an address NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-location-address-state​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' A state specified in an address NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-location-address​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' A (part of the) address of the location NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-location-name​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' A portion of the location's name or alias NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-medicationdispense-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The identity of a patient to list dispenses for NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-medicationdispense-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Returns dispenses with a specified dispense status NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-medicationdispense-type​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Returns dispenses of a specific type NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-medicationrequest-authoredon​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Return prescriptions written on this date NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-medicationrequest-encounter​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Return prescriptions with this encounter identifier NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-medicationrequest-intent​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Returns prescriptions with different intents NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-medicationrequest-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Returns prescriptions for a specific patient NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-medicationrequest-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Status of the prescription NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-observation-category​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The classification of the type of observation NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-observation-code​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The code of the observation type NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-observation-date​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Obtained date/time. If the obtained element is a period, a date that falls in the period NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-observation-lastupdated​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' When the resource version last changed NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-observation-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The subject that the observation is about (if patient) NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-observation-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The status of the observation NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-organization-address​.htmlinformationThe html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: ' multipleOr : True (Conformance Expectation = MAY)' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-organization-name​.htmlinformationThe html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: ' multipleOr : True (Conformance Expectation = MAY)' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-patient-birthdate​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The patient's date of birth NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-patient-death-date​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The date of death has been provided and satisfies this search value NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-patient-family​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' A portion of the family name of the patient NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-patient-given​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' A portion of the given name of the patient NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-patient-id.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Logical id of this artifact NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-patient-identifier​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' A patient identifier NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-patient-name​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' A server defined search that may match any of the string fields in the HumanName, including family, give, prefix, suffix, suffix, and/or text NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-practitioner-id​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Logical id of this artifact NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-practitioner-identifier​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' A practitioner's Identifier NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-practitioner-name​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' A server defined search that may match any of the string fields in the HumanName, including family, give, prefix, suffix, suffix, and/or text NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-practitionerrole-practitioner​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Practitioner that is able to provide the defined services for the organization NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-practitionerrole-specialty​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The practitioner has this specialty at an organization NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-procedure-code​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' A code to identify a procedure NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-procedure-date​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' When the procedure was performed NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-procedure-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Search by subject - a patient NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-procedure-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-questionnaireresponse-authored​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' When the questionnaire response was last changed NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-questionnaireresponse-id​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Logical id of this artifact NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-questionnaireresponse-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The patient that is the subject of the questionnaire response NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-questionnaireresponse-questionnaire​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The questionnaire the answers are provided for NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-questionnaireresponse-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The status of the questionnaire response NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-race.htmlinformationThe html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: ' multipleOr : True (Conformance Expectation = MAY)' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-relatedperson-id​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Logical id of this artifact NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-relatedperson-name​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' A server defined search that may match any of the string fields in the HumanName, including family, give, prefix, suffix, suffix, and/or text NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-relatedperson-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The patient this related person is related to NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-servicerequest-authored​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Date request signed NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-servicerequest-category​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Classification of service NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-servicerequest-code​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' What is being requested/ordered NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-servicerequest-id​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Logical id of this artifact NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-servicerequest-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Search by subject - a patient NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-servicerequest-status​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' draft | active | on-hold | revoked | completed | entered-in-error | unknown NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-specimen-id​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Logical id of this artifact NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
SearchParameter-us-core-specimen-patient​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' The patient the specimen comes from NOTE: This SearchParameter is defined only to document Server and Client expectations. Its definition is derived from the standard FHIR SearchParameter and it uses the Conformance expectation extension to define additional expectations for the following SearchParameter elements: multipleAnd multipleOr comparator modifier chain It SHALL NOT be used as a search parameter for search. Servers and Clients SHOULD use the standard FHIR SearchParameter. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-head-occipital-frontal-circumference-percentile​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Pediatric Head Occipital Frontal Circumference Percentile Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record, search, and fetch pediatric head occipital frontal circumference (OFC) percentile observations associated with a patient from birth to 37 Months of age using a standard LOINC code and UCUM units of measure. It specifies which additional core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-pediatric-bmi-for-age​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Pediatric BMI for Age Observation Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record, search, and fetch pediatric body mass index (BMI) percentile per age and sex for youth 2-20 observations in FHIR using a standard LOINC code and UCUM units of measure. It specifies which additional core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-pediatric-weight-for-height​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' US Core Pediatric Weight for Height Observation Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record, search, and fetch pediatric weight-for-length per age and sex observations in FHIR with a standard LOINC code and UCUM units of measure. It specifies which additional core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-adi-documentreference​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Advance Directive Information (ADI) DocumentReference Profile inherits from the FHIR DocumentReference resource; refer to it for scope and usage definitions. This profile and the US Core Observation ADI Documentation Profile meet the U.S. Core Data for Interoperability (USCDI) Advance Directive Observation Data Element requirements. It sets minimum expectations for searching and fetching patient Advance Directive Information (ADI) documents using the DocumentReference resource. Examples of advance healthcare directive documents include physician order for life sustaining treatment (POLST), do not resuscitate order (DNR), and medical power of attorney. In addition to the document contents, it communicates the type of advance directive document, the author, the verifier, and other properties. To represent whether advance directive documents exist for a patient, see the US Core Observation ADI Documentation Profile. This profile sets minimum expectations for searching and fetching patient ADI documents using the DocumentReference resource. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-allergyintolerance​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core AllergyIntolerance Profile inherits from the FHIR AllergyIntolerance resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the AllergyIntolerance resource to record, search, and fetch allergies/adverse reactions associated with a patient. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-average-blood-pressure​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Average Blood Pressure Profile inherits from the Observation resource; refer to it for scope and usage definitions. This profile sets minimum expectations for recording, searching, and fetching average diastolic and systolic blood pressure observations with standard LOINC codes and UCUM units of measure. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-blood-pressure​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' US Core Blood Pressure Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record, search, and fetch diastolic and systolic blood pressure observations with standard LOINC codes and UCUM units of measure. It specifies which additional core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-bmi.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core BMI Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record, search, and fetch Body Mass Index (BMI) observations with a standard LOINC codes and UCUM units of measure. It specifies which additional core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-body-height​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Body Height Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record, search, and fetch body height observations with a standard LOINC code and UCUM units of measure. It specifies which additional core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-body-temperature​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Body Temperature Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record, search, and fetch body temperature observations with a standard LOINC code and UCUM units of measure. It specifies which additional core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-body-weight​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Body Weight Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record, search, and fetch body weight observations with a standard LOINC code and UCUM units of measure. It specifies which additional core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-care-experience-preference​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Care Experience Preference Profile inherits from the FHIR Observation resource; refer to This profile provides guidance on how to record a care experience preference expressed by the patient regarding their care and treatment. Examples include, but are not limited to, religious preferences, dislikes and fears, preferred place for birth, preferred pharmacy, and thoughts and feelings to be shared. This profile does not represent an actual order, but it can guide caregivers and medical personnel about what is important for the person. This profile sets minimum expectations for the Observation resource to record, search, and fetch for a patient care experience preferences. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-careplan​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core CarePlan Profile inherits from the FHIR CarePlan resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the CarePlan resource to record, search, and fetch assessment and plan of treatment data associated with a patient. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-careteam​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core CareTeam Profile inherits from the FHIR CareTeam resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the CareTeam resource for identifying the Care Team members associated with a patient to promote interoperability and adoption through common implementation. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-condition-encounter-diagnosis​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Condition Encounter Diagnosis Profile inherits from the FHIR Condition resource; refer to it for scope and usage definitions. US Core version 5.0.0 split the US Core Condition Profile into this profile and the US Core Condition Problems and Health Concerns Profile. This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) Encounter Diagnosis Data Element. It sets minimum expectations for the Condition resource to record, search, and fetch information about an encounter diagnosis. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-condition-problems-health-concerns​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Condition Problems and Health Concerns Profile inherits from the FHIR Condition resource; refer to it for scope and usage definitions. US Core version 5.0.0 split the US Core Condition Profile into this profile and the US Core Condition Encounter Diagnosis Profile. This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) Problems, Health Concerns, and SDOH Problems/Health Concerns Data Elements. It sets minimum expectations for the Condition resource to record, search, and fetch information about a condition, diagnosis, or another event, situation, issue, or clinical concept documented and categorized as a problem or health concern, including information about a Social Determinants of Health related condition. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-coverage​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Coverage Profile inherits from the FHIR Coverage resource; refer to it for scope and usage definitions. This profile meets the requirements of the US Core Data for Interoperability (USCDI) Health Insurance Information Data Class. It sets minimum expectations for the Coverage resource to record, search, and fetch data related to an individual's insurance coverage for health care. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-diagnosticreport-lab​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core DiagnosticReport Profile for Laboratory Results Reporting inherits from the FHIR DiagnosticReport resource; refer to it for scope and usage definitions. Laboratory results are grouped and summarized using the DiagnosticReport resource, which typically references Observation resource(s). Each Observation resource represents an individual laboratory test and result value or component result values or a nested panel (such as a microbial susceptibility panel) that references other observations. Laboratory results can also be presented in report form or as free text. This profile sets minimum expectations for the DiagnosticReport resource to record, search, and fetch laboratory results associated with a patient. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-diagnosticreport-note​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core DiagnosticReport Profile for Report and Note Exchange inherits from the FHIR DiagnosticReport resource; refer to it for scope and usage definitions. This profile sets minimum expectations for searching and fetching Diagnostic Reports and Notes using the DiagnosticReport resource. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. Before reviewing this profile, implementers are encouraged to read the Clinical Notes Guidance to understand the overlap of the US Core DiagnosticReport Profile for Report and Note exchange and the US Core DocumentReference Profile. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-documentreference​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core DocumentReference Profile inherits from the FHIR DocumentReference resource; refer to it for scope and usage definitions. This profile sets minimum expectations for searching and fetching patient documents including Clinical Notes using the DocumentReference resource. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. Before reviewing this profile, implementers are encouraged to read the Clinical Notes Guidance to understand the overlap of the US Core DiagnosticReport Profile for Report and Note exchange and the US Core DocumentReference Profile. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-encounter​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Encounter Profile inherits from the FHIR Encounter resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the Encounter resource to record, search, and fetch basic encounter information for an individual patient. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-genderIdentity​.htmlinformationThe html source contains the word 'SHOULD NOT' but it is not in a text phrase marked as a conformance clause: ' This extension is no longer a USCDI requirement and is deprecated. It SHOULD NOT be used for new or revised content. It is retained for historical/backward compatibility purposes. Implementers can use the HL7 standard extension instead ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-goal.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Goal Profile inherits from the FHIR Goal resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the Goal resource to record, search, and fetch Goal information associated with a patient. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-head-circumference​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Head Circumference Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record, search, and fetch head circumference observations with a standard LOINC code and UCUM units of measure. It specifies which additional core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-heart-rate​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Heart Rate Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record, search, and fetch heart rate observations with a standard LOINC code and UCUM units of measure. It specifies which additional core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-immunization​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Immunization Profile inherits from the FHIR Immunization resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the Immunization resource to record, search, and fetch immunization history associated with a patient. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-implantable-device​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Device Profile inherits from the FHIR Device resource; refer to it for scope and usage definitions. This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) Unique Device Identifier - Implantable Data Element. It sets minimum expectations for the Device resource to record, search, and fetch UDI information associated with a patient's implantable device(s). It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-location​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Location Profile inherits from the FHIR Location resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the Location resource for recording, searching, and fetching a "physical place of available services or resources." It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-medication​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Medication Profile inherits from the FHIR Medication resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the Medication resource to record, search, and fetch medications associated with a patient. When referencing a medication, the MedicationRequest resource can use a code or refer to this profile. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-medicationdispense​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core MedicationDispense Profile inherits from the FHIR MedicationDispense resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the MedicationDispense resource to record, search, and fetch the state of a patients medication with regards to dispensing or other activity. (e.g., dispensed, partially dispensed, not dispensed) It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-medicationrequest​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core MedicationRequest Profile inherits from the FHIR MedicationRequest resource; refer to it for scope and usage definitions. This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) Medications Data Class. This profile sets minimum expectations for the MedicationRequest resource to record, search, and fetch a patient's medication prescriptions or orders. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-observation-adi-documentation​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Observation Advance Directive Information (ADI) Documentation Profile inherits from the FHIR Observation resource; refer to it for scope and usage definitions. This profile and the US Core Observation ADI DocumentationReference Profile meet the U.S. Core Data for Interoperability (USCDI) Advance Directive Observation Data Element requirements. It is used to communicate whether a person has advance directive information (ADI) and, if one or more documents exist, their location. Examples of advance healthcare directive documents include physician order for life sustaining treatment (POLST), do not resuscitate order (DNR), and medical power of attorney. To communicate the type of advance directive document, the author, the verifier, and other properties, see the US Core ADI DocumentReference Profile. This profile sets minimum expectations for the Observation resource to record, search, and fetch findings about the presence of a patient's advance directives. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-observation-clinical-result​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Observation Clinical Result Profile is based upon the core FHIR Observation Resource and, along with the US Core DiagnosticReport Profile, meets the US Core Data for Interoperability (USCDI) requirements for Diagnostic Imaging and Clinical Tests Data Classes. This profile sets minimum expectations for the Observation resource to record and search non-laboratory clinical test results (e.g., radiology and other clinical observations generated from procedures). An example would be when a gastroenterologist reports the size of a polyp observed during a colonoscopy. This profile is the basis for the US Core Laboratory Result Observation Profile, which defines additional data elements to record and search laboratory test results. The US Core Observation Clinical Result Profile sets minimum expectations to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-observation-lab​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Laboratory Result Observation Profile is based upon the US Core Observation Clinical Result Profile and, along with the US Core DiagnosticReport Profile for Laboratory Results Reporting, meets the U.S. Core Data for Interoperability (USCDI) Laboratory requirements. Laboratory results are grouped and summarized using the DiagnosticReport resource, which references Observation resources. Each Observation resource represents an individual laboratory test and result value, a “nested” panel (such as a microbial susceptibility panel) that references other observations, or rarely a laboratory test with component result values. The US Core Laboratory Result Observation Profile sets minimum expectations for the Observation resource to record, search, and fetch laboratory test results associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-observation-occupation​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Observation Occupation Profile inherits from the FHIR Observation resource; refer to it for scope and usage definitions. This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) Occupation and Occupation Industry Data Elements. It sets minimum expectations for the Observation resource to record, search, and fetch a patient's past or present job as occupation and industry, in other words, the type of work and type of business that compensates for work or assigns work to an unpaid worker or volunteer. In the context of this profile, a job is defined as a work situation or a training or volunteer position held for a specified period. This profile specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-observation-pregnancyintent​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Observation Pregnancy Intent Profile inherits from the FHIR Observation resource; refer to it for scope and usage definitions. This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) Pregnancy Status Data Element. This profile sets minimum expectations for the Observation resource to record, search, and fetch the patient's intention to become pregnant. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-observation-pregnancystatus​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Pregnancy Status Observation Profile inherits from the FHIR Observation resource; refer to it for scope and usage definitions. This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) Pregnancy Status Data Element. It sets minimum expectations for the Observation resource to record, search, and fetch the patient's state or condition of being pregnant. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-observation-screening-assessment​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Observation Screening Assessment Profile inherits from the FHIR Observation resource; refer to it for scope and usage definitions. Beginning with US Core Version 6.0.0, this profile supersedes the US Core Observation Survey Profile (see the Changes Between Versions page for a summary of cross-version comparisons of US Core Profiles). This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) Health Status Assessments Data Class. It sets the minimum expectations for the Observation Resource to record, search, and fetch observations representing the questions and responses to surveys and screening and assessment tools. For example, a social history status such as education or food insecurity or an assessment of cognitive, functional, or disability status. It can represent a single response, multiple responses, and multi-select "check all that apply" type questions. This profile specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. Before reviewing this profile, implementers are encouraged to read the Screening and Assessments guidance page, which documents the process of recording responses and capturing assertions/determinations resulting from surveys and questionnaires. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-observation-sexual-orientation​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Observation Sexual Orientation Profile inherits from the FHIR Observation resource; refer to refer to it for scope and usage definitions. This Profile sets minimum expectations for the Observation resource to record, search, and fetch sexual orientation observations associated with a patient. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-organization​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Organization Profile inherits from the FHIR Organization resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the Organization resource to record, search, and fetch patient or provider organziation information. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-patient​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Patient Profile inherits from the FHIR Patient resource; refer to it for scope and usage definitions. This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) Patient Demographics/Information Data Class. It sets minimum expectations for the Patient resource to record, search, and fetch basic demographics and other administrative information about an individual patient. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-practitioner​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Practitioner Profile inherits from the FHIR Practitioner resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the Practitioner resource to record, search, and fetch basic demographics and administrative information about an individual practitioner. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-practitionerrole​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core PractitionerRole Profile inherits from the FHIR PractitionerRole resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the PractitionerRole Resource to record, search, and fetch the practitioner role information. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. The requirements for the US Core Practitioner were drawn from the Argonaut Provider Directory, IHE Healthcare Provider Directory and the ONC Provider Directory Workshop. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-procedure​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Procedure Profile inherits from the FHIR Procedure resource; refer to it for scope and usage definitions. This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) Procedures Data Class. It sets minimum expectations for the Procedure resource to record, search, and fetch procedure information associated with a patient. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-provenance​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Provenance Profile inherits from the FHIR Provenance resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the Provenance resource to record, search, and fetch provenance information associated with a record. It covers the minimal (basic) information to support lineage of information. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Before reviewing this profile, implementers are encouraged to read the Basic Provenance guidance page, which documents several key use cases, specifically, the organization responsible for the most recent action on the resource. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-pulse-oximetry​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Pulse Oximetry Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record, search, and pulse oximetry and inspired oxygen observations with standard LOINC codes and UCUM units of measure. It specifies which additional core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-questionnaireresponse​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core QuestionaireResponse Profile inherits from the Structured Data Capture (SDC) Questionnaire Response Profile. This profile sets minimum expectations for the QuestionnaireResponse resource to record, search, and fetch retrieve captures the responses to form/survey and assessment tools such as the Protocol for Responding to and Assessing Patients\u2019 Assets, Risks, and Experiences (PRAPARE) Survey. It specifies which core additional elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Before reviewing this profile, implementers are encouraged to read the Screening and Assessments guidance page, which documents the process of recording responses and capturing assertions/determinations resulting from surveys and questionnaires. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-relatedperson​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core RelatedPerson Profile inherits from the FHIR RelatedPerson resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the RelatedPerson resource to record, search, and fetch basic administrative information about persons with a legal or familial relationship to a patient. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-respiratory-rate​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Respiratory Rate Profile inherits from the US Core Vital Signs Profile. This profile sets minimum expectations for the Observation resource to record, search, and fetch respiratory rate observations with a standard LOINC code and UCUM units of measure. It specifies which additional core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-servicerequest​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core ServiceRequest Profile inherits from the FHIR ServiceRequest resource; refer to it for scope and usage definitions. This profile sets minimum expectations for recording, searching, and fetching the ServiceRequest information. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-sex.htmlinformationThe html source contains the word 'SHOULD NOT' but it is not in a text phrase marked as a conformance clause: ' This extension is no longer a USCDI requirement and is deprecated. It SHOULD NOT be used for new or revised content. It is retained for historical/backward compatibility purposes. Implementers SHOULD use the US Core Individual Sex Extension instead. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-simple-observation​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Simple Observation Profile inherits from the FHIR Observation resource; refer to it for scope and usage definitions. This US Core FHIR Profile captures any "simple" observations not covered by other US Core Observation profiles. It represents any observation not classified as vital signs, laboratory, imaging, or other specific observation types. This profile sets minimum expectations for the Observation resource to record, search, and retrieve observations such as a clinical observation or assertion about patient health status or other general observations. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-smokingstatus​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Smoking Status Observation Profile inherits from the FHIR Observation resource; refer to it for scope and usage definitions. This profile meets the requirements of the U.S. Core Data for Interoperability (USCDI) Smoking Status Data Element. This profile sets minimum expectations for the Observation resource to record, search, and fetch smoking status data associated with a patient. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-specimen​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Specimen Profile inherits from the FHIR Specimen resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the Specimen resource to record, search, and fetch information about substances associated with a patient being sampled or tested (such as nasopharyngeal swab, whole blood, or serum). It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-treatment-intervention-preference​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' The US Core Treatment Intervention Preference Profile inherits from the FHIR Observation resource; refer to it for scope and usage definitions. This profile provides guidance on how to record a treatment intervention preference expressed by the patient regarding their personal health goals, preferences, and priorities for medical treatments or interventions in the event of a future health scenario where a person is unable to make medical decisions because of a severe illness or injury. This profile does not represent an actual order, but it can guide caregivers and medical personnel about what is important for the person. This profile sets minimum expectations for the Observation resource to record, search, and fetch for patient treatment intervention preferences. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. ' CONFORMANCE_STATEMENT_WORD
StructureDefinition-us-core-vital-signs​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' This profile is based on the base FHIR Vital Signs Profile and defines additional constraints on the Observation resource to represent vital signs observations. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. This US Core profiles that are derived from this profile are listed below. ' CONFORMANCE_STATEMENT_WORD
ValueSet-us-core-screening-assessment-condition-category​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' This value set consists of the single code "sdoh". It is the minimum value set of category codes used in the US Core Condition Problems and Health Concerns Profile that any conformant system SHALL support to help identify the type of USCDI Health Status/Assessment data class being reported. ' CONFORMANCE_STATEMENT_WORD
ValueSet-us-core-screening-assessment-observation-category​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' This value set is the minimum value set of category codes used in the US Core Observation Screening Assessment and Simple Observation Profiles that any conformant system SHALL support to help identify the type of USCDI Health Status/Assessment data class being reported. ' CONFORMANCE_STATEMENT_WORD
ValueSet-us-core-screening-assessment-observation-maximum-category​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: ' This value set is a value set of category codes used in the US Core Observation Screening Assessment that any conformant system SHOULD support to help identify the type of USCDI Health Status/Assessment data class being reported. ' CONFORMANCE_STATEMENT_WORD
ValueSet-us-core-simple-observation-category​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: ' This value set is a value set of category codes used in the US Core Simple Observation and Condition Problems and Health Concerns Profiles that any conformant system SHOULD support to help identify the type of USCDI Health Status/Assessment data class being reported. ' CONFORMANCE_STATEMENT_WORD
artifacts.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' This operation is used to return all the references to documents related to a patient. It is invoked on a FHIR Server's DocumentReference endpoint (e.g., [base]/DocumentReference/$docref) and operates across all DocumentReference instances. The operation requires a patient id and takes the optional input parameters: start date end date document type on-demand profile and returns a searchset Bundle containing DocumentReference resources for the patient. If the server has stored documents or can create documents for the patient and those documents are available for the user, the server returns the DocumentReference resources associated with documents. This operation's intended use is to provide a way for providers or patients to access their available documents. The document itself can be subsequently retrieved using the link provided in the DocumentReference.content.attachment.url element. The link could be a FHIR endpoint to a Binary Resource or some other document repository. This operation is different from a FHIR RESTful query on DocumentReference by patient and type and date range because: It is used to request a server to generate a document based on the specified parameters. If no parameters are specified, the server SHALL return a DocumentReference to the patient's current C-CDA CCD. If the server cannot generate a document based on the specified parameters, the operation will return an empty search bundle. Unless the client indicates they are only interested in 'on-demand' documents using the on-demand parameter, the server SHOULD return DocumentReference instances for existing documents that meet the request parameters In this regard, this operation is similar to a FHIR RESTful query. ' CONFORMANCE_STATEMENT_WORD
basic-provenance.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'The timestamp and pointer (i.e., target) to the appropriate Resource are required in all cases and must be included. This IG would note these as SHALL constraints if systems always had the Author and Author Organizations available. Participants in the development of this guide reported that the Author information provided to HIEs needs to be more consistent and reliable.' CONFORMANCE_STATEMENT_WORD
changes-between-versions.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Servers SHOULD maintain a stable common identifier for a resource across versions.' CONFORMANCE_STATEMENT_WORD
changes.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Applied: (Correction) Typo "service should happen" instead of "serviceSHOULDhappen" FHIR-49068 See Changes Here' CONFORMANCE_STATEMENT_WORD
clinical-notes.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Servers SHALL support, at minimum, these ten "Common Clinical Notes":' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-allergyintolerance-us-core-allergyintolerance​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-birthsex-us-core-birthsex​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-careplan-us-core-careplan​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-condition-us-core-condition-encounter-diagnosis​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-condition-us-core-condition-problems-health-concerns​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-device-us-core-implantable-device​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-diagnosticreport-us-core-diagnosticreport-lab​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-diagnosticreport-us-core-diagnosticreport-note​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-documentreference-us-core-documentreference​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-ethnicity-us-core-ethnicity​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.' vs 'The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-goal-us-core-goal​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-immunization-us-core-immunization​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-medication-us-core-medication​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-observationresults-us-core-observation-clinical-result​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-observationresults-us-core-observation-lab​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-patient-us-core-patient​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-procedure-us-core-procedure​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-race-us-core-race​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.' vs 'The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-smokingstatus-us-core-smokingstatus​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/sd-argo-vitalsigns-us-core-vital-signs​.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'' CONFORMANCE_STATEMENT_WORD
comparison-argo​/vs-observation-ccdavitalsignresult-2​.16​.840​.1​.113883​.3​.88​.12​.80​.62​.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: 'This value set indicates the allowed vital sign result types. The vocabulary selected for this value set based on ONC 2015 Edition Common Clinical Data Set (CCDS) for vitals. Note the concept Blood pressure systolic and diastolic (55284-4) is used to group the related observations Systolic blood pressure (8480-6) and Diastolic blood pressure (8462-4). It SHALL NOT be used alone, but both 8480-6 and 8462-2 SHALL also be valued.' CONFORMANCE_STATEMENT_WORD
downloads.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'The following package file includes an NPM package file used by many of the FHIR tools. It contains all the value sets, profiles, extensions, list of pages and URLs in the IG, etc., defined as part of this version of the Implementation Guides. This file SHOULD be the first choice whenever generating any implementation artifacts since it contains all the rules about what makes the profiles valid. Implementers must still be familiar with the specification content and profiles that apply to create a conformant implementation. See the validating profiles and resources documentation in FHIR for more information.' CONFORMANCE_STATEMENT_WORD
general-guidance.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'The search expectations and US Core Profiles have been developed and tested using logical FHIR ids. Therefore, a reference to a US Core resource SHOULD include a logical id (Reference.reference), not an identifier (Reference.identifier).' CONFORMANCE_STATEMENT_WORD
general-requirements.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'This page documents requirements common to all US Core actors in this guide. The conformance verbs - SHALL, SHOULD, MAY - used in this guide are defined in FHIR Conformance Rules.' CONFORMANCE_STATEMENT_WORD
index.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'The US Core Implementation Guide is based on FHIR Version R4. It defines the minimum constraints on the FHIR resources to create the US Core Profiles. The elements, extensions, vocabularies, and value sets that SHALL be present are identified, and how they are used is defined. It also documents the minimum FHIR RESTful interactions for each US Core Profiles to access patient data. Establishing the "floor" of standards to promote interoperability and adoption through common implementation allows for further standards development evolution for specific use cases. There are two different ways to implement US Core:' CONFORMANCE_STATEMENT_WORD
medication-list.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'This guide supports representing a medication using a code or a reference to a Medication resource. Typically, a code will be for a branded (for example, Crestor 10mg tablet) or a generic (for example, Rosuvastatin 10mg tablet) medication. When using a code, the code SHALL follow the extensible binding rules to Medication Clinical Drug (RxNorm) - i.e., unless RxNorm does not cover the concept, the RxNorm code SHALL be used. USCDI recommends the National Drug Codes (NDC) as an optional medication terminology. They can be supplied as an additional coding element. More information about using codes can be found in the General Guidance and the FHIR Terminology sections. A medication resource is typically used when information not included in the RxNorm code is required. For example, the Medication resource is the only way to represent compounded correctly or extemporaneously prepared medication. When referencing the Medication resource, the resource may be included in the returned bundle, as an external resource, or as a contained resource if it can't stand alone. These options are shown in Figure 3 below. The Server application MAY choose any combination of these methods, but if an external reference to Medication is used, the Server SHALL support the _include parameter for searching this element. The Client application MUST support all methods. The MedicationRequest examples show these different methods. Additional guidance is provided below and in the US Core Server CapabilityStatement section.' CONFORMANCE_STATEMENT_WORD
must-support.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'For querying and reading US Core Profiles, Must Support on any profile data element SHALL be interpreted as follows (see the US Core Roadmap page for writing and updating US Core Profiles):' CONFORMANCE_STATEMENT_WORD
patient-data-feed.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Servers SHALL implement at least one of these approaches and document which one(s) they use. In either case, typical examples of changes that may trigger notifications include:' CONFORMANCE_STATEMENT_WORD
profiles-and-extensions.htmlinformationThe html source contains the word 'SHOULD NOT' but it is not in a text phrase marked as a conformance clause: 'The following extensions are not used in any US Core Profile and are deprecated. They SHOULD NOT be used for new or revised content. They are retained for historical/backward compatibility purposes.' CONFORMANCE_STATEMENT_WORD
scopes.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'US Core Servers SHALL Support Token Introspection' CONFORMANCE_STATEMENT_WORD
screening-and-assessments.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'However, implementers SHOULD consider more constrained, domain-specific profiles derived from the US Core Profiles to meet the needs of their respective use cases.' CONFORMANCE_STATEMENT_WORD
search-parameters-and-operations.htmlinformationThe html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: 'They SHALL NOT be interpreted as search parameters for search. Servers and Clients SHOULD use the standard FHIR SearchParameters.' CONFORMANCE_STATEMENT_WORD
security.htmlinformationThe html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Implementers SHOULD be aware of these security considerations associated with FHIR transactions, particularly those related to:' CONFORMANCE_STATEMENT_WORD
terminology.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'See the FHIR terminology section for a complete discussion on code systems and a list of code system names used in FHIR. Most code systems used in this guide are defined in the base FHIR specification. However, the following code systems are unique to this guide and not listed in the base FHIR specification. If a URI is listed here, it SHALL be used in the US Core profiles to identify the code system in preference to any other code system URI.' CONFORMANCE_STATEMENT_WORD
us-core-roadmap.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'The US Core FHIR Profiles are designed to be the base set of requirements for FHIR implementation in the US. All US Realm implementation guides SHALL use the US Core Profiles or SHALL explicitly state why they are unable to use them. Throughout the development of US Core, implementers, the government, and the clinical community have brought forward additional requirements. This section outlines the approach to growth and a place for items that may be added to US Core.' CONFORMANCE_STATEMENT_WORD
writing-vital-signs.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Servers SHALL document support for writing Observation resources in their Capability Statements by including a CapabilityStatement.rest.resource[type=Observation].interaction with a code of create. Servers that support the ability to update Observation resources SHALL also include an interaction with a code of update.' CONFORMANCE_STATEMENT_WORD

fsh-generated/includes Show Validation Information (0)


fsh-generated/includes/fsh-link-references.md Show Validation Information (0)


fsh-generated/includes/fsh-link-references.md Show Validation Information (0)


fsh-generated/includes/menu.xml Show Validation Information (0)


fsh-generated/includes/menu.xml Show Validation Information (0)


fsh-generated/resources/ImplementationGuide-hl7.fhir.us.core.json Show Validation Information (1)

PathSeverityMessageValidating
ImplementationGuide​.dependsOn[3] (l1​/c4852)warningThe ImplementationGuide uses package hl7.fhir.uv.sdc#3.0.0 released on 2022-03-08, but the most recent appropriate version is 4.0.0. This reference is getting old and the more recent version should be considered IG_DEPENDENCY_VERSION_WARNING_OLD--

input/data/README.md Show Validation Information (0)


input/data/additional-uscdi-requirements.csv Show Validation Information (0)


input/data/addl_uscdi_choice_refs.csv Show Validation Information (0)


input/data/addl_uscdi_refs.csv Show Validation Information (0)


input/data/assessments-valuesets.csv Show Validation Information (0)


input/data/codesystem-ref-all-list.csv Show Validation Information (0)


input/data/codesystems.yml Show Validation Information (0)


input/data/dstu2-r4-table.csv Show Validation Information (0)


input/data/ig.yml Show Validation Information (0)


input/data/ms_choice_refs.csv Show Validation Information (0)


input/data/ms_refs.csv Show Validation Information (0)


input/data/new_stuff.yml Show Validation Information (0)


input/data/provenance-elements.csv Show Validation Information (0)


input/data/scopes.csv Show Validation Information (0)


input/data/source.yml Show Validation Information (0)


input/data/uscdi-examples.yml Show Validation Information (0)


input/data/uscdi-table.csv Show Validation Information (0)


input/data/uscore-sps.csv Show Validation Information (0)


input/data/valueset-ref-all-list.csv Show Validation Information (0)


input/data/vsacname-fhiruri-map.csv Show Validation Information (0)


input/examples/AHC-HRSN-item-example-68517-2.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Device-defib.json Show Validation Information (2)


input/examples/Device-knee.json Show Validation Information (2)


input/examples/DiagnosticReport-bone-density-report.json Show Validation Information (2)


input/examples/DiagnosticReport-cardiology-report.json Show Validation Information (2)


input/examples/DiagnosticReport-chest-xray-report.json Show Validation Information (2)


input/examples/DocumentReference-adi-dnr.json Show Validation Information (2)


input/examples/DocumentReference-living-will.json Show Validation Information (2)


input/examples/DocumentReference-polst.json Show Validation Information (2)


input/examples/Observation-10-minute-apgar-color.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#32401-2) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-10-minute-apgar-heart-rate.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#32402-0) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-10-minute-apgar-muscle-tone.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#32403-8) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-10-minute-apgar-reflex-irritability.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#32404-6) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-10-minute-apgar-respiratory-effort.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#32405-3) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-10-minute-apgar-score.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#9271-8) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-10-minute-apgar-score-panel.json Show Validation Information (2)


input/examples/Observation-AUDIT-C-item-example-68517-2.json Show Validation Information (2)


input/examples/Observation-AUDIT-C-item-example-68519-8.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.code (l21/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#68519-8) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-AUDIT-C-item-example-68520-6.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.code (l21/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#68520-6) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-AUDIT-C-item-example-75626-2.json Show Validation Information (2)


input/examples/Observation-AUDIT-C-panel-example-72109-2.json Show Validation Information (2)


input/examples/Observation-EVS-item-example-68516-4.json Show Validation Information (2)


input/examples/Observation-EVS-item-example-89555-7.json Show Validation Information (2)


input/examples/Observation-EVS-panel-example-89574-8.json Show Validation Information (2)


input/examples/Observation-HVS-item-example-88122-7.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-HVS-item-example-88123-5.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-HVS-item-example-88124-3.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-HVS-panel-example-88121-9.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PHQ9-item-example-44250-9.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[1] (l20/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PHQ9-item-example-44251-7.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[1] (l20/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PHQ9-item-example-44252-5.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[1] (l20/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PHQ9-item-example-44253-3.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[1] (l20/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PHQ9-item-example-44254-1.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[1] (l20/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PHQ9-item-example-44255-8.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[1] (l20/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PHQ9-item-example-44258-2.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[1] (l20/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PHQ9-item-example-44259-0.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[1] (l20/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PHQ9-item-example-44260-8.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[1] (l20/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PHQ9-item-example-44261-6.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[1] (l20/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PHQ9-item-example-69722-7.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[1] (l20/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PHQ9-panel-example-44249-1.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[1] (l20/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-54899-0.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#54899-0) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-56051-6.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#56051-6) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-56799-0.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#56799-0) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-63512-8.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#63512-8) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-63586-2.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#63586-2) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-67875-5.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#67875-5) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-71802-3.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-76437-3.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#76437-3) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-76501-6.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-82589-3.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#82589-3) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-93026-3.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-93027-1.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-93028-9.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-93029-7.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-93030-5.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-93033-9.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-93034-7.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-93035-4.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-item-example-93038-8.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#93038-8) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-multiselect-item-example-32624-9-answer0.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#32624-9) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-multiselect-item-example-32624-9-answer1.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile
Observation.code (l22/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#32624-9) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-multiselect-item-example-93031-3-answer0.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-multiselect-item-example-93031-3-answer1.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-panel-example-93025-5.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-panel-example-93039-6.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-panel-example-93040-4.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-panel-example-93041-2.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-panel-example-93042-0.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-PRAPARE-panel-example-93043-8.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.category[0] (l3/c6)informationNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-TAPS-item-example-75889-6.json Show Validation Information (2)


input/examples/Observation-TAPS-item-example-88037-7.json Show Validation Information (2)


input/examples/Observation-TAPS-item-example-96842-0.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.code (l21/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#96842-0) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-TAPS-item-example-96843-8.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.code (l21/c4)informationNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#96843-8) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Observation Screening Assessment Profile

input/examples/Observation-TAPS-item-example-96844-6.json Show Validation Information (2)


input/examples/Observation-TAPS-panel-example-96841-2.json Show Validation Information (2)


input/examples/Observation-alcohol-use-status.json Show Validation Information (2)


input/examples/Observation-alcoholic-drinks-per-day.json Show Validation Information (2)


input/examples/Observation-average-blood-pressure.json Show Validation Information (2)


input/examples/Observation-care-experience-preference.json Show Validation Information (2)


input/examples/Observation-exercise-per-day.json Show Validation Information (2)


input/examples/Observation-exercise-per-week.json Show Validation Information (2)


input/examples/Observation-simple-observation-cognitive-status.json Show Validation Information (2)


input/examples/Observation-simple-observation-disability-status.json Show Validation Information (2)


input/examples/Observation-simple-observation-functional-status.json Show Validation Information (2)


input/examples/Observation-simple-observation-sdoh.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.code (l21/c4)informationNone of the codings provided are in the value set 'LOINC Codes' (http://hl7.org/fhir/ValueSet/observation-codes|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#160695008) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Simple Observation Profile

input/examples/Observation-substance-use-status.json Show Validation Information (2)

PathSeverityMessageValidating
Observation.code (l28/c4)informationNone of the codings provided are in the value set 'LOINC Codes' (http://hl7.org/fhir/ValueSet/observation-codes|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#228366006) (from server, see log, or see the servers logic) Terminology_TX_NoValid_3_CCUS Core Simple Observation Profile

input/examples/Observation-treatment-intervention-preference.json Show Validation Information (2)


input/examples/PractitionerRole_Practitioner_Endpoint_Bundle_Example.json Show Validation Information (7)


input/examples/Procedure-R4-defib-implant.json Show Validation Information (2)


input/examples/Questionnaire-AUDIT-C.json Show Validation Information (1)


input/examples/Questionnaire-TAPS.json Show Validation Information (1)


input/examples/Questionnaire-exercise-vital-sign.json Show Validation Information (1)


input/examples/Questionnaire-hunger-vital-sign-example.json Show Validation Information (1)

PathSeverityMessageValidating
Questionnaire​.code[0]​.display (l1​/c15309)errorWrong Display Name 'Hunger Vital Sign [HVS]' for http://loinc.org#88121-9. Valid display is one of 2 choices: 'Children's HealthWatch Hunger Vital Sign [HVS]' (en-US) or 'Children's HealthWatch Hunger Vital Sign [HVS]' (en-US) (for the language(s) 'en-US') (from https://tx.fhir.org/r4, see log, or see the servers logic) Display_Name_for__should_be_one_of__instead_ofSDCBaseQuestionnaire

input/examples/Questionnaire-phq-9-example.json Show Validation Information (1)


input/examples/Questionnaire-prapare-example.json Show Validation Information (1)


input/examples/QuestionnaireResponse-AUDIT-C.json Show Validation Information (2)


input/examples/QuestionnaireResponse-PRAPARE-example.json Show Validation Information (2)


input/examples/QuestionnaireResponse-TAPS.json Show Validation Information (2)


input/examples/QuestionnaireResponse-exercise-vital-sign.json Show Validation Information (2)


input/examples/QuestionnaireResponse-glasgow-coma-score.json Show Validation Information (2)


input/examples/QuestionnaireResponse-hunger-vital-sign-example.json Show Validation Information (2)


input/examples/QuestionnaireResponse-phq-9-example.json Show Validation Information (2)


input/examples/Specimen-example-serum-hemolyzed.json Show Validation Information (2)


input/examples/allergyintolerance-example.json Show Validation Information (2)


input/examples/allergyintolerance-non-pharmacologic-agent-example.json Show Validation Information (2)


input/examples/allergyintolerance-provenance-example1.json Show Validation Information (5)


input/examples/allergyintolerance-provenance-example2.json Show Validation Information (5)


input/examples/at-home-in-vitro-test.json Show Validation Information (2)


input/examples/blood-pressure.json Show Validation Information (2)


input/examples/bmi.json Show Validation Information (2)


input/examples/bp-data-absent.json Show Validation Information (2)


input/examples/bundle-docref-example1.json Show Validation Information (3)


input/examples/bundle-docref-example2.json Show Validation Information (7)


input/examples/capillary-refill-time-nail-bed.json Show Validation Information (2)


input/examples/careteam-example.json Show Validation Information (2)


input/examples/colonoscopy.json Show Validation Information (2)


input/examples/condition-SDOH-example.json Show Validation Information (2)


input/examples/condition-duodenal-ulcer.json Show Validation Information (2)


input/examples/condition-encounter-diagnosis-example1.json Show Validation Information (2)


input/examples/condition-encounter-diagnosis-example2.json Show Validation Information (2)


input/examples/coverage-example.json Show Validation Information (2)


input/examples/diagnosticreport-cbc.json Show Validation Information (2)


input/examples/diagnosticreport-metabolic-panel.json Show Validation Information (2)


input/examples/documentreference-discharge-summary.json Show Validation Information (2)


input/examples/dxa-femur-l-armass-bmd.json Show Validation Information (2)


input/examples/dxa-femur-l-t-score-bmd.json Show Validation Information (2)


input/examples/dxa-femur-l-z-score-bmd.json Show Validation Information (2)


input/examples/dxa-hip-l-armass-bmd.json Show Validation Information (2)


input/examples/dxa-hip-l-t-score-bmd.json Show Validation Information (2)


input/examples/dxa-hip-l-z-score-bmd.json Show Validation Information (2)


input/examples/ekg-impression.json Show Validation Information (2)


input/examples/ekg-lead.json Show Validation Information (2)


input/examples/encounter-1036.json Show Validation Information (2)

PathSeverityMessageValidating
Encounter​.hospitalization​.dischargeDisposition (l33​/c6)informationNone of the codings provided are in the value set 'USEncounterDischargeDisposition' (http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition|5.0.0), and a coding is recommended to come from this value set (codes = http://terminology.hl7.org/CodeSystem/nubc-UB92#01) Terminology_TX_NoValid_3_CCUS Core Encounter Profile

input/examples/encounter-delivery.json Show Validation Information (2)


input/examples/encounter-example-1.json Show Validation Information (2)


input/examples/episode-summary.json Show Validation Information (2)


input/examples/example-organization-2.json Show Validation Information (2)


input/examples/goal-1.json Show Validation Information (2)


input/examples/goal-sdoh-2.json Show Validation Information (2)


input/examples/head-circumference.json Show Validation Information (2)


input/examples/health-concern-example.json Show Validation Information (2)


input/examples/heart-rate.json Show Validation Information (2)


input/examples/heart-rate-rhythm.json Show Validation Information (2)


input/examples/height.json Show Validation Information (2)


input/examples/hl7east.json Show Validation Information (2)


input/examples/imm-1.json Show Validation Information (2)


input/examples/jugular-vein-distension.json Show Validation Information (2)


input/examples/length.json Show Validation Information (2)


input/examples/library-uscore-3.1.1-model-definition.json Show Validation Information (1)


input/examples/library-uscore-4.0.0-model-definition.json Show Validation Information (1)


input/examples/library-uscore-5.0.1-model-definition.json Show Validation Information (1)


input/examples/library-uscore-6.1.0-model-definition.json Show Validation Information (1)


input/examples/library-uscore-7.0.0-model-definition.json Show Validation Information (1)


input/examples/library-uscore-8.0.1-model-definition.json Show Validation Information (1)


input/examples/location-hospital.json Show Validation Information (2)


input/examples/media-chest-xray.json Show Validation Information (1)


input/examples/media-ekg-strip.json Show Validation Information (1)


input/examples/medicationdispense-example.json Show Validation Information (2)

PathSeverityMessageValidating
MedicationDispense​.medication​.ofType(CodeableConcept)​.coding[0]​.system (l10​/c4)warningA definition for CodeSystem 'http://www.nlm.nih.gov/research/umls/rxnorm' version '09022025' could not be found, so the code cannot be validated. Valid versions: 03022026 (from https://tx.fhir.org/r4, see log, or see the servers logic) UNKNOWN_CODESYSTEM_VERSIONUS Core MedicationDispense Profile

input/examples/medicationrequest-coded-oral-axid.json Show Validation Information (2)

PathSeverityMessageValidating
MedicationRequest​.medication​.ofType(CodeableConcept)​.coding[0]​.system (l58​/c4)warningA definition for CodeSystem 'http://www.nlm.nih.gov/research/umls/rxnorm' version '09022025' could not be found, so the code cannot be validated. Valid versions: 03022026 (from https://tx.fhir.org/r4, see log, or see the servers logic) UNKNOWN_CODESYSTEM_VERSIONUS Core MedicationRequest Profile

input/examples/medicationrequest-contained-oral-axid.json Show Validation Information (4)


input/examples/medicationrequest-referenced-oral-axid.json Show Validation Information (2)


input/examples/medicationrequest-self-tylenol.json Show Validation Information (2)

PathSeverityMessageValidating
MedicationRequest​.medication​.ofType(CodeableConcept)​.coding[0]​.system (l54​/c4)warningA definition for CodeSystem 'http://www.nlm.nih.gov/research/umls/rxnorm' version '09022025' could not be found, so the code cannot be validated. Valid versions: 03022026 (from https://tx.fhir.org/r4, see log, or see the servers logic) UNKNOWN_CODESYSTEM_VERSIONUS Core MedicationRequest Profile

input/examples/missing-coded-data-example.json Show Validation Information (2)


input/examples/observation-ADI-example.json Show Validation Information (2)


input/examples/observation-cbc-erythrocytes.json Show Validation Information (2)


input/examples/observation-cbc-hematocrit.json Show Validation Information (2)


input/examples/observation-cbc-hemoglobin.json Show Validation Information (2)


input/examples/observation-cbc-leukocytes.json Show Validation Information (2)


input/examples/observation-cbc-mch.json Show Validation Information (2)


input/examples/observation-cbc-mchc.json Show Validation Information (2)


input/examples/observation-cbc-mcv.json Show Validation Information (2)


input/examples/observation-cbc-platelets.json Show Validation Information (2)


input/examples/observation-no-ADI-example.json Show Validation Information (2)


input/examples/observation-occupation.json Show Validation Information (2)


input/examples/observation-occupation-industry-unknown.json Show Validation Information (2)


input/examples/observation-occupation-unknown.json Show Validation Information (2)


input/examples/observation-pregnancy-intent.json Show Validation Information (2)


input/examples/observation-pregnancy-status.json Show Validation Information (2)


input/examples/observation-satO2-fiO2.json Show Validation Information (2)


input/examples/observation-serum-bun.json Show Validation Information (2)


input/examples/observation-serum-calcium.json Show Validation Information (2)


input/examples/observation-serum-chloride.json Show Validation Information (2)


input/examples/observation-serum-co2.json Show Validation Information (2)


input/examples/observation-serum-creatinine.json Show Validation Information (2)


input/examples/observation-serum-glucose.json Show Validation Information (2)


input/examples/observation-serum-potassium.json Show Validation Information (2)


input/examples/observation-serum-sodium.json Show Validation Information (2)


input/examples/observation-xray-chest-findings.json Show Validation Information (2)


input/examples/observation-xray-chest-impression.json Show Validation Information (2)


input/examples/ofc-percentile.json Show Validation Information (2)


input/examples/organization-acme-lab.json Show Validation Information (2)


input/examples/organization-acme-payer.json Show Validation Information (2)


input/examples/organization-holy-healthcare.json Show Validation Information (2)


input/examples/oxygen-saturation.json Show Validation Information (2)


input/examples/p-r-interval-ekg-lead.json Show Validation Information (2)


input/examples/packs-years-example.json Show Validation Information (2)


input/examples/patient-child-example.json Show Validation Information (2)


input/examples/patient-deceased-example.json Show Validation Information (2)


input/examples/patient-example.json Show Validation Information (2)


input/examples/patient-infant-example.json Show Validation Information (2)


input/examples/pediatric-bmi-example.json Show Validation Information (2)


input/examples/pediatric-wt-example.json Show Validation Information (2)


input/examples/practitioner-1.json Show Validation Information (2)


input/examples/practitioner-2.json Show Validation Information (2)


input/examples/practitioner-pharmacist.json Show Validation Information (2)


input/examples/procedure-rehab.json Show Validation Information (2)


input/examples/pulse-intensity-palpation.json Show Validation Information (2)


input/examples/q-t-interval-ekg-lead.json Show Validation Information (2)


input/examples/qrs-dur-ekg-lead.json Show Validation Information (2)


input/examples/relatedperson-shaw-niece.json Show Validation Information (2)


input/examples/respiratory-rate.json Show Validation Information (2)


input/examples/saint-luke-w-endpoint.json Show Validation Information (3)


input/examples/servicerequest-bmp.json Show Validation Information (2)


input/examples/servicerequest-cbc.json Show Validation Information (2)


input/examples/servicerequest-chest-xray.json Show Validation Information (2)


input/examples/servicerequest-ekg.json Show Validation Information (2)


input/examples/servicerequest-foodpantry-referral.json Show Validation Information (2)


input/examples/servicerequest-rehab.json Show Validation Information (2)


input/examples/some-day-smoker.json Show Validation Information (2)


input/examples/specimen-example-serum.json Show Validation Information (2)


input/examples/specimen-example-urine.json Show Validation Information (2)


input/examples/specimen-example-whole-blood.json Show Validation Information (2)


input/examples/temperature.json Show Validation Information (2)


input/examples/udi-1.json Show Validation Information (2)


input/examples/urobilinogen.json Show Validation Information (2)


input/examples/uscore-med1.json Show Validation Information (2)

PathSeverityMessageValidating
Medication​.code​.coding[0]​.system (l9​/c4)warningA definition for CodeSystem 'http://www.nlm.nih.gov/research/umls/rxnorm' version '09022025' could not be found, so the code cannot be validated. Valid versions: 03022026 (from https://tx.fhir.org/r4, see log, or see the servers logic) UNKNOWN_CODESYSTEM_VERSIONUS Core Medication Profile

input/examples/uscore-med2.json Show Validation Information (2)

PathSeverityMessageValidating
Medication​.code​.coding[0]​.system (l9​/c4)warningA definition for CodeSystem 'http://www.nlm.nih.gov/research/umls/rxnorm' version '09022025' could not be found, so the code cannot be validated. Valid versions: 03022026 (from https://tx.fhir.org/r4, see log, or see the servers logic) UNKNOWN_CODESYSTEM_VERSIONUS Core Medication Profile

input/examples/weight.json Show Validation Information (2)


input/images Show Validation Information (0)


input/images/ArgoR4Meds_1.svg Show Validation Information (0)


input/images/ArgoR4Meds_3.svg Show Validation Information (0)


input/images/ArgoR4Meds_4.svg Show Validation Information (0)


input/images/DiagnosticReport_DocumentReference_Resource_Overlap.png Show Validation Information (0)


input/images/Must_Support_AllergyIntolerance.png Show Validation Information (0)


input/images/Must_Support_AllergyIntolerance_clinicalStatus.png Show Validation Information (0)


input/images/Must_Support_AllergyIntolerance_code.png Show Validation Information (0)


input/images/Must_Support_Condition_category.png Show Validation Information (0)


input/images/Must_Support_Condition_code.png Show Validation Information (0)


input/images/Must_Support_DiagnosticReport_category.png Show Validation Information (0)


input/images/Must_Support_DiagnosticReport_issued.png Show Validation Information (0)


input/images/Must_Support_DiagnosticReport_presentedForm.png Show Validation Information (0)


input/images/Must_Support_Differential_View.png Show Validation Information (0)


input/images/Must_Support_DocumentReference.png Show Validation Information (0)


input/images/Must_Support_DocumentReference_category.png Show Validation Information (0)


input/images/Must_Support_Key_View.png Show Validation Information (0)


input/images/Must_Support_MedicationRequest.reported.png Show Validation Information (0)


input/images/Must_Support_Observation.effective.png Show Validation Information (0)


input/images/Must_Support_Observation.value.png Show Validation Information (0)


input/images/Must_Support_Organization_identifier.png Show Validation Information (0)


input/images/Must_Support_Patient_name.png Show Validation Information (0)


input/images/Must_Support_Patient_telecom.png Show Validation Information (0)


input/images/Must_Support_Snapshot_View.png Show Validation Information (0)


input/images/Must_Support_vital_signs.performer.png Show Validation Information (0)


input/images/Provenance_HIE_Multi_Org_Device.svg Show Validation Information (0)


input/images/Provenance_HIE_Single_Org_Device.svg Show Validation Information (0)


input/images/Provenance_Recon_Single_Organization.svg Show Validation Information (0)


input/images/Provenance_Recon_Workflow_Step2.svg Show Validation Information (0)


input/images/README.md Show Validation Information (0)


input/images/USCDI.png Show Validation Information (0)


input/images/US_Core_Growth_Path.jpg Show Validation Information (0)


input/images/allergies-and-intolerances.png Show Validation Information (0)


input/images/argo_proposed_screening_and_assessments.png Show Validation Information (0)


input/images/basic_fhir_restful_interaction.svg Show Validation Information (0)


input/images/both-url.jpg Show Validation Information (0)


input/images/care-team-members.png Show Validation Information (0)


input/images/clinical-notes.png Show Validation Information (0)


input/images/clinical-tests.png Show Validation Information (0)


input/images/comparison-argo Show Validation Information (0)


input/images/comparison-argo/OperationOutcome-vsac-errors.json Show Validation Information (0)


input/images/comparison-argo/administration.jpg Show Validation Information (0)


input/images/comparison-argo/administration-module-person.png Show Validation Information (0)


input/images/comparison-argo/ansi.png Show Validation Information (0)


input/images/comparison-argo/ansi-approved.gif Show Validation Information (0)


input/images/comparison-argo/cc0.png Show Validation Information (0)


input/images/comparison-argo/clinical.png Show Validation Information (0)


input/images/comparison-argo/clinicalreasoning-components-diagram.jpg Show Validation Information (0)


input/images/comparison-argo/clinicalreasoning-integrating-decision-support-conversation.png Show Validation Information (0)


input/images/comparison-argo/clinicalreasoning-integrating-decision-support-radiology-request.png Show Validation Information (0)


input/images/comparison-argo/clinicalreasoning-integrating-decision-support-service-scenario.png Show Validation Information (0)


input/images/comparison-argo/clinicalreasoning-integrating-decision-support-simple-request.png Show Validation Information (0)


input/images/comparison-argo/clinicalreasoning-knowledge-artifact-components.png Show Validation Information (0)


input/images/comparison-argo/compare-to-r3.png Show Validation Information (0)


input/images/comparison-argo/conf-optional.png Show Validation Information (0)


input/images/comparison-argo/conf-prohibited.png Show Validation Information (0)


input/images/comparison-argo/conf-required.png Show Validation Information (0)


input/images/comparison-argo/conformance.jpg Show Validation Information (0)


input/images/comparison-argo/conparison-zip-marker.bin Show Validation Information (0)


input/images/comparison-argo/cross.png Show Validation Information (0)


input/images/comparison-argo/diagnostics.jpg Show Validation Information (0)


input/images/comparison-argo/download.gif Show Validation Information (0)


input/images/comparison-argo/dragon.png Show Validation Information (0)


input/images/comparison-argo/exchange.png Show Validation Information (0)


input/images/comparison-argo/external.png Show Validation Information (0)


input/images/comparison-argo/extra-type.png Show Validation Information (0)


input/images/comparison-argo/favicon.png Show Validation Information (0)


input/images/comparison-argo/fhir.css Show Validation Information (0)


input/images/comparison-argo/fhir-logo.png Show Validation Information (0)


input/images/comparison-argo/fhir-logo-n.png Show Validation Information (0)


input/images/comparison-argo/fhir-logo-www.png Show Validation Information (0)


input/images/comparison-argo/fhir-table-scripts.js Show Validation Information (0)


input/images/comparison-argo/fhr.icns Show Validation Information (0)


input/images/comparison-argo/financial.png Show Validation Information (0)


input/images/comparison-argo/foundation.png Show Validation Information (0)


input/images/comparison-argo/header-tabs.png Show Validation Information (0)


input/images/comparison-argo/help.png Show Validation Information (0)


input/images/comparison-argo/help16.png Show Validation Information (0)


input/images/comparison-argo/hl7-logo.png Show Validation Information (0)


input/images/comparison-argo/hl7logo.png Show Validation Information (0)


input/images/comparison-argo/icon-administration.png Show Validation Information (0)


input/images/comparison-argo/icon-change-add.png Show Validation Information (0)


input/images/comparison-argo/icon-change-edit.png Show Validation Information (0)


input/images/comparison-argo/icon-change-remove.png Show Validation Information (0)


input/images/comparison-argo/icon-clinical.png Show Validation Information (0)


input/images/comparison-argo/icon-dictionary.png Show Validation Information (0)


input/images/comparison-argo/icon-directory.gif Show Validation Information (0)


input/images/comparison-argo/icon-documentation.png Show Validation Information (0)


input/images/comparison-argo/icon-error.gif Show Validation Information (0)


input/images/comparison-argo/icon-example.png Show Validation Information (0)


input/images/comparison-argo/icon-fhir-1024.png Show Validation Information (0)


input/images/comparison-argo/icon-fhir-128.png Show Validation Information (0)


input/images/comparison-argo/icon-fhir-16.png Show Validation Information (0)


input/images/comparison-argo/icon-fhir-16-grey.png Show Validation Information (0)


input/images/comparison-argo/icon-fhir-24.png Show Validation Information (0)


input/images/comparison-argo/icon-fhir-32.png Show Validation Information (0)


input/images/comparison-argo/icon-fhir-48.png Show Validation Information (0)


input/images/comparison-argo/icon-fhir-64.png Show Validation Information (0)


input/images/comparison-argo/icon-fhir-720.png Show Validation Information (0)


input/images/comparison-argo/icon-implementation.png Show Validation Information (0)


input/images/comparison-argo/icon-include.png Show Validation Information (0)


input/images/comparison-argo/icon-infrastructure.png Show Validation Information (0)


input/images/comparison-argo/icon-key.png Show Validation Information (0)


input/images/comparison-argo/icon-list.gif Show Validation Information (0)


input/images/comparison-argo/icon-not-selected.png Show Validation Information (0)


input/images/comparison-argo/icon-object-box.png Show Validation Information (0)


input/images/comparison-argo/icon-page.png Show Validation Information (0)


input/images/comparison-argo/icon-q-attachment.png Show Validation Information (0)


input/images/comparison-argo/icon-q-boolean.png Show Validation Information (0)


input/images/comparison-argo/icon-q-choice.png Show Validation Information (0)


input/images/comparison-argo/icon-q-coding.png Show Validation Information (0)


input/images/comparison-argo/icon-q-date.png Show Validation Information (0)


input/images/comparison-argo/icon-q-datetime.png Show Validation Information (0)


input/images/comparison-argo/icon-q-decimal.png Show Validation Information (0)


input/images/comparison-argo/icon-q-display.png Show Validation Information (0)


input/images/comparison-argo/icon-q-group.png Show Validation Information (0)


input/images/comparison-argo/icon-q-integer.png Show Validation Information (0)


input/images/comparison-argo/icon-q-item.png Show Validation Information (0)


input/images/comparison-argo/icon-q-open-choice.png Show Validation Information (0)


input/images/comparison-argo/icon-q-quantity.png Show Validation Information (0)


input/images/comparison-argo/icon-q-reference.png Show Validation Information (0)


input/images/comparison-argo/icon-q-string.png Show Validation Information (0)


input/images/comparison-argo/icon-q-text.png Show Validation Information (0)


input/images/comparison-argo/icon-q-time.png Show Validation Information (0)


input/images/comparison-argo/icon-q-url.png Show Validation Information (0)


input/images/comparison-argo/icon-qi-help.png Show Validation Information (0)


input/images/comparison-argo/icon-qi-hidden.png Show Validation Information (0)


input/images/comparison-argo/icon-qi-horizontal.png Show Validation Information (0)


input/images/comparison-argo/icon-qi-instructions.png Show Validation Information (0)


input/images/comparison-argo/icon-qi-observation.png Show Validation Information (0)


input/images/comparison-argo/icon-qi-optional.png Show Validation Information (0)


input/images/comparison-argo/icon-qi-readonly.png Show Validation Information (0)


input/images/comparison-argo/icon-qi-security.png Show Validation Information (0)


input/images/comparison-argo/icon-qi-security.bmp Show Validation Information (0)


input/images/comparison-argo/icon-qi-subject.png Show Validation Information (0)


input/images/comparison-argo/icon-qi-vertical.png Show Validation Information (0)


input/images/comparison-argo/icon-resource.png Show Validation Information (0)


input/images/comparison-argo/icon-selected.png Show Validation Information (0)


input/images/comparison-argo/icon-toc.png Show Validation Information (0)


input/images/comparison-argo/icon-warning.png Show Validation Information (0)


input/images/comparison-argo/icon_bundle.png Show Validation Information (0)


input/images/comparison-argo/icon_choice.gif Show Validation Information (0)


input/images/comparison-argo/icon_datatype.gif Show Validation Information (0)


input/images/comparison-argo/icon_element.gif Show Validation Information (0)


input/images/comparison-argo/icon_entry_blue.png Show Validation Information (0)


input/images/comparison-argo/icon_extension.png Show Validation Information (0)


input/images/comparison-argo/icon_extension_complex.png Show Validation Information (0)


input/images/comparison-argo/icon_extension_simple.png Show Validation Information (0)


input/images/comparison-argo/icon_fixed.gif Show Validation Information (0)


input/images/comparison-argo/icon_group.png Show Validation Information (0)


input/images/comparison-argo/icon_modifier_extension_complex.png Show Validation Information (0)


input/images/comparison-argo/icon_modifier_extension_simple.png Show Validation Information (0)


input/images/comparison-argo/icon_page.gif Show Validation Information (0)


input/images/comparison-argo/icon_page-child.gif Show Validation Information (0)


input/images/comparison-argo/icon_page_n.gif Show Validation Information (0)


input/images/comparison-argo/icon_page_n_c.gif Show Validation Information (0)


input/images/comparison-argo/icon_page_n_i.gif Show Validation Information (0)


input/images/comparison-argo/icon_page_n_o.gif Show Validation Information (0)


input/images/comparison-argo/icon_page_n_p.gif Show Validation Information (0)


input/images/comparison-argo/icon_primitive.png Show Validation Information (0)


input/images/comparison-argo/icon_profile.png Show Validation Information (0)


input/images/comparison-argo/icon_q_item.png Show Validation Information (0)


input/images/comparison-argo/icon_q_root.gif Show Validation Information (0)


input/images/comparison-argo/icon_reference.png Show Validation Information (0)


input/images/comparison-argo/icon_resource.png Show Validation Information (0)


input/images/comparison-argo/icon_reuse.png Show Validation Information (0)


input/images/comparison-argo/icon_slice.png Show Validation Information (0)


input/images/comparison-argo/icon_slice_item.png Show Validation Information (0)


input/images/comparison-argo/icon_text.png Show Validation Information (0)


input/images/comparison-argo/icon_vd_col.png Show Validation Information (0)


input/images/comparison-argo/icon_vd_foreach.png Show Validation Information (0)


input/images/comparison-argo/icon_vd_select.png Show Validation Information (0)


input/images/comparison-argo/icon_vd_union.png Show Validation Information (0)


input/images/comparison-argo/icon_vd_view.png Show Validation Information (0)


input/images/comparison-argo/ig-r4.jsonX Show Validation Information (0)


input/images/comparison-argo/implsupport.png Show Validation Information (0)


input/images/comparison-argo/index.html Show Validation Information (0)


input/images/comparison-argo/index.png Show Validation Information (0)


input/images/comparison-argo/information.png Show Validation Information (0)


input/images/comparison-argo/link.svg Show Validation Information (0)


input/images/comparison-argo/linked-data.png Show Validation Information (0)


input/images/comparison-argo/lock.png Show Validation Information (0)


input/images/comparison-argo/logo.png Show Validation Information (0)


input/images/comparison-argo/logo_ansinew.jpg Show Validation Information (0)


input/images/comparison-argo/mappingSpaces.details Show Validation Information (0)


input/images/comparison-argo/medication.png Show Validation Information (0)


input/images/comparison-argo/modifier.png Show Validation Information (0)


input/images/comparison-argo/modifier-extension-warning.png Show Validation Information (0)


input/images/comparison-argo/mustsupport.png Show Validation Information (0)


input/images/comparison-argo/new.png Show Validation Information (0)


input/images/comparison-argo/normative.png Show Validation Information (0)


input/images/comparison-argo/npm.png Show Validation Information (0)


input/images/comparison-argo/npm16.png Show Validation Information (0)


input/images/comparison-argo/npm24.png Show Validation Information (0)


input/images/comparison-argo/page.png Show Validation Information (0)


input/images/comparison-argo/page.gif Show Validation Information (0)


input/images/comparison-argo/prism.css Show Validation Information (0)


input/images/comparison-argo/prism.js Show Validation Information (0)


input/images/comparison-argo/publication-request.json Show Validation Information (0)


input/images/comparison-argo/qa.png Show Validation Information (0)


input/images/comparison-argo/reasoning.png Show Validation Information (0)


input/images/comparison-argo/resource-groupings.json Show Validation Information (0)


input/images/comparison-argo/rss.png Show Validation Information (0)


input/images/comparison-argo/sd-argo-allergyintolerance-us-core-allergyintolerance.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-birthsex-us-core-birthsex.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-careplan-us-core-careplan.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-condition-us-core-condition-encounter-diagnosis.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-condition-us-core-condition-problems-health-concerns.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-device-us-core-implantable-device.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-diagnosticreport-us-core-diagnosticreport-lab.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-diagnosticreport-us-core-diagnosticreport-note.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-documentreference-us-core-documentreference.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-ethnicity-us-core-ethnicity.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-goal-us-core-goal.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-immunization-us-core-immunization.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-medication-us-core-medication.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-observationresults-us-core-observation-clinical-result.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-observationresults-us-core-observation-lab.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-patient-us-core-patient.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-procedure-us-core-procedure.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-race-us-core-race.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-smokingstatus-us-core-smokingstatus.html Show Validation Information (0)


input/images/comparison-argo/sd-argo-vitalsigns-us-core-vital-signs.html Show Validation Information (0)


input/images/comparison-argo/search.png Show Validation Information (0)


input/images/comparison-argo/secpriv.jpg Show Validation Information (0)


input/images/comparison-argo/security-icon-app.png Show Validation Information (0)


input/images/comparison-argo/security-icon-fhir.png Show Validation Information (0)


input/images/comparison-argo/security-icon-sec.png Show Validation Information (0)


input/images/comparison-argo/security-icon-user.png Show Validation Information (0)


input/images/comparison-argo/spec.internals Show Validation Information (0)


input/images/comparison-argo/strip.png Show Validation Information (0)


input/images/comparison-argo/stripe.png Show Validation Information (0)


input/images/comparison-argo/summary.png Show Validation Information (0)


input/images/comparison-argo/target.png Show Validation Information (0)


input/images/comparison-argo/tbl-closed.png Show Validation Information (0)


input/images/comparison-argo/tbl-open.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000001.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000010000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001001.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000010010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000101.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000011.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000111.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000011100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000111000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001110000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000111001.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001110010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000011101.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000111010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001110100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000111011.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001110110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001111.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000011110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000111100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000011110000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001111001.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000011110010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000111101.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001111010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000011111.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000111110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001111100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000011111000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001111101.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000011111010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000111110100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000011111011.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000111110110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0000111111.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001111110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000011111100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00001111111.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000011111110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0001.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00011.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck000110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck001.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck001000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0010000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck001001.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0010010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00101.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck001010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0011.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck00110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck01.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck01000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0101.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck01010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck010100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck01011.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck010110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck011.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck01100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck011000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0110000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck011001.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0110010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck01101.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck011010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0110100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck011011.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0110110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck01101100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0110111.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck01101110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0111.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck01110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck011100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck01111.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck011110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0111100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck011110000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck01111001.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck011110010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0111101.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck01111010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck011111.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0111110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck012.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0240.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck02400.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0241.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck02410.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck025.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0250.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck02500.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck025000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck02501.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck025010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0250240.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck025025.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0250250.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck02503.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0251.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck02510.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck02512.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0251240.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck025125.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0251250.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0251252.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck02513.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck03.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0320.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck033.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0330.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck03300.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0331.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck03310.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0340.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck03400.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0341.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck03410.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck035.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0350.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck03500.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0350240.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck035025.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0350250.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck03503.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0351.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck03510.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck03512.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0351240.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck035125.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0351250.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0351252.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck03513.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck04.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck040.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0400.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck041.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0410.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck05.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck050.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0500.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck05040.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0505.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck05050.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck051.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0510.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0512.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck05140.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck0515.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck05150.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck05152.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck100000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10001.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck100010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1001.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck100100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1001000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10010000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1001001.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10010010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck100101.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1001010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10011.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck100110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck101.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck101000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10101.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck101010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1011.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck101100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1011000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10110000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1011001.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10110010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck101101.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1011010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10111.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck101110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1011100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck101111.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1011110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10120.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1013.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10130.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10240.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1025.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck10250.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck103.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1040.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck105.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1050.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck11.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck11000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck110000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck11001.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck110010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1101.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck11010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck110100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck11011.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck110110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck111.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck11100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck111000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck11101.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck111010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1111.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck11110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck111100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1111000.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck111101.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1111010.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck11111.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck111110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck112.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1120.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck11240.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1125.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck11250.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck11252.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck113.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1130.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1140.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck115.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1150.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1152.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck12.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck120.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck124.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1240.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck12400.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1241.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck12410.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck125.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1250.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck12500.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1251.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck12510.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck125100.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck12511.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck125110.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck12512.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1252.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck13.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck130.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1320.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck133.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1330.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck134.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck14.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck140.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1400.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck141.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1410.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1424.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck143.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck15.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck150.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1500.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck15040.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1505.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck15050.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck151.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1510.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1512.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck15140.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1515.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck15150.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck15152.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck152.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1540.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck15424.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1543.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck155.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1550.png Show Validation Information (0)


input/images/comparison-argo/tbl_bck1552.png Show Validation Information (0)


input/images/comparison-argo/tbl_blank.png Show Validation Information (0)


input/images/comparison-argo/tbl_spacer.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin-closed.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin-open.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin_end.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin_end-closed.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin_end-open.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin_end_slice.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin_end_slice-closed.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin_end_slice-open.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin_end_slicer.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin_end_slicer-closed.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin_end_slicer-open.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin_slice.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin_slice-closed.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin_slice-open.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin_slicer.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin_slicer-closed.png Show Validation Information (0)


input/images/comparison-argo/tbl_vjoin_slicer-open.png Show Validation Information (0)


input/images/comparison-argo/tbl_vline.png Show Validation Information (0)


input/images/comparison-argo/tbl_vline_slice.png Show Validation Information (0)


input/images/comparison-argo/tbl_vline_slicer.png Show Validation Information (0)


input/images/comparison-argo/terminology.png Show Validation Information (0)


input/images/comparison-argo/tick.png Show Validation Information (0)


input/images/comparison-argo/tick2.gif Show Validation Information (0)


input/images/comparison-argo/validation-oo.json Show Validation Information (0)


input/images/comparison-argo/validation-summary.json Show Validation Information (0)


input/images/comparison-argo/vs-c80-doc-typecodes-us-core-documentreference-type.html Show Validation Information (0)


input/images/comparison-argo/vs-condition-category-condition-category.html Show Validation Information (0)


input/images/comparison-argo/vs-device-kind-device-kind.html Show Validation Information (0)


input/images/comparison-argo/vs-formatcodes-v3-HL7FormatCodes.html Show Validation Information (0)


input/images/comparison-argo/vs-languages-Languages.html Show Validation Information (0)


input/images/comparison-argo/vs-medication-codes-2.16.840.1.113762.1.4.1010.4.html Show Validation Information (0)


input/images/comparison-argo/vs-narrative-status-us-core-narrative-status.html Show Validation Information (0)


input/images/comparison-argo/vs-observation-ccdavitalsignresult-2.16.840.1.113883.3.88.12.80.62.html Show Validation Information (0)


input/images/comparison-argo/vs-observation-codes-2.16.840.1.113762.1.4.1267.6.html Show Validation Information (0)


input/images/comparison-argo/vs-observation-codes-us-core-laboratory-test-codes.html Show Validation Information (0)


input/images/comparison-argo/vs-observation-status-us-core-observation-smoking-status-status.html Show Validation Information (0)


input/images/comparison-argo/vs-procedure-type-us-core-procedure-code.html Show Validation Information (0)


input/images/comparison-argo/vs-report-codes-us-core-diagnosticreport-report-and-note-codes.html Show Validation Information (0)


input/images/comparison-argo/vs-report-codes-us-core-laboratory-test-codes.html Show Validation Information (0)


input/images/comparison-argo/vs-vacc-status-immunization-status.html Show Validation Information (0)


input/images/comparison-argo/warning.png Show Validation Information (0)


input/images/comparison-argo/workflow.png Show Validation Information (0)


input/images/comparison-argo/xver-paths-1.0.json Show Validation Information (0)


input/images/comparison-argo/xver-paths-1.4.json Show Validation Information (0)


input/images/comparison-argo/xver-paths-3.0.json Show Validation Information (0)


input/images/comparison-argo/xver-paths-4.0.json Show Validation Information (0)


input/images/comparison-argo/xver-paths-5.0.json Show Validation Information (0)


input/images/comparison-argo/xver-paths-r2.json Show Validation Information (0)


input/images/cross_red_circle.svg.png Show Validation Information (0)


input/images/diagnostic-imaging.png Show Validation Information (0)


input/images/encounter.png Show Validation Information (0)


input/images/facility-information.png Show Validation Information (0)


input/images/fhir-write1.svg Show Validation Information (0)


input/images/fhir-write2.svg Show Validation Information (0)


input/images/goals-and-preferences.png Show Validation Information (0)


input/images/green_checkmark.svg.png Show Validation Information (0)


input/images/health-insurance-information.png Show Validation Information (0)


input/images/health-status-assessments.png Show Validation Information (0)


input/images/immunizations.png Show Validation Information (0)


input/images/includelines Show Validation Information (0)


input/images/laboratory.png Show Validation Information (0)


input/images/medical-devices.png Show Validation Information (0)


input/images/medications.png Show Validation Information (0)


input/images/minus_symbol.svg.png Show Validation Information (0)


input/images/modifier-element-view.png Show Validation Information (0)


input/images/observation.png Show Validation Information (0)


input/images/orange_checkmark.svg.png Show Validation Information (0)


input/images/orders.png Show Validation Information (0)


input/images/org_logo.png Show Validation Information (0)


input/images/org_logo_hl7.png Show Validation Information (0)


input/images/patient-demographics.png Show Validation Information (0)


input/images/patient-summary-and-plan.png Show Validation Information (0)


input/images/problems.png Show Validation Information (0)


input/images/procedures.png Show Validation Information (0)


input/images/provenance.png Show Validation Information (0)


input/images/relationships.svg Show Validation Information (0)


input/images/screening_and_assessments.svg Show Validation Information (0)


input/images/sdoh_condition.svg Show Validation Information (0)


input/images/tables Show Validation Information (0)


input/images/tables/additional-uscdi-requirements.xlsx Show Validation Information (0)


input/images/tables/additional-uscdi-requirements.csv Show Validation Information (0)


input/images/tables/addl_uscdi_choice_refs.csv Show Validation Information (0)


input/images/tables/addl_uscdi_choice_refs.xlsx Show Validation Information (0)


input/images/tables/addl_uscdi_refs.csv Show Validation Information (0)


input/images/tables/addl_uscdi_refs.xlsx Show Validation Information (0)


input/images/tables/assessments-valuesets.csv Show Validation Information (0)


input/images/tables/assessments-valuesets.xlsx Show Validation Information (0)


input/images/tables/codesystem-ref-all-list.csv Show Validation Information (0)


input/images/tables/codesystem-ref-all-list.xlsx Show Validation Information (0)


input/images/tables/dstu2-r4-table.xlsx Show Validation Information (0)


input/images/tables/dstu2-r4-table.csv Show Validation Information (0)


input/images/tables/ms_choice_refs.xlsx Show Validation Information (0)


input/images/tables/ms_choice_refs.csv Show Validation Information (0)


input/images/tables/ms_refs.csv Show Validation Information (0)


input/images/tables/ms_refs.xlsx Show Validation Information (0)


input/images/tables/provenance-elements.xlsx Show Validation Information (0)


input/images/tables/provenance-elements.csv Show Validation Information (0)


input/images/tables/scopes.csv Show Validation Information (0)


input/images/tables/scopes.xlsx Show Validation Information (0)


input/images/tables/uscdi-table.csv Show Validation Information (0)


input/images/tables/uscdi-table.xlsx Show Validation Information (0)


input/images/tables/uscore-sps.csv Show Validation Information (0)


input/images/tables/uscore-sps.xlsx Show Validation Information (0)


input/images/tables/valueset-ref-all-list.xlsx Show Validation Information (0)


input/images/tables/valueset-ref-all-list.csv Show Validation Information (0)


input/images/tables/vsacname-fhiruri-map.csv Show Validation Information (0)


input/images/tables/vsacname-fhiruri-map.xlsx Show Validation Information (0)


input/images/todo.png Show Validation Information (0)


input/images/uscore-observation-assessment-structure.svg Show Validation Information (0)


input/images/vital-signs.png Show Validation Information (0)


input/images/vsac-1.png Show Validation Information (0)


input/images/vsac-2.png Show Validation Information (0)


input/images/vsac-3.png Show Validation Information (0)


input/images/yearly-updates.png Show Validation Information (0)


input/images/yellow_checkmark.svg.png Show Validation Information (0)


input/includes/DAR-exception.md Show Validation Information (0)


input/includes/SDOH_search_transaction.md Show Validation Information (0)


input/includes/ValueSet-expansion-note.md Show Validation Information (0)


input/includes/additional-codings.md Show Validation Information (0)


input/includes/additional-requirements-intro.md Show Validation Information (0)


input/includes/additional-uscdi-tabler.md Show Validation Information (0)


input/includes/assessment-category-table-generator.html Show Validation Information (0)


input/includes/assessment-valueset-table-generator.html Show Validation Information (0)


input/includes/assessment_examples.md Show Validation Information (0)


input/includes/boilerplate-clia-warning.md Show Validation Information (0)


input/includes/ccds_table.md Show Validation Information (0)


input/includes/codesystem-ref-all-table-generator.html Show Validation Information (0)


input/includes/condition-quickstart.md Show Validation Information (0)


input/includes/conditional-goals-guidance.md Show Validation Information (0)


input/includes/conform-patient.md Show Validation Information (0)


input/includes/diagnosticreport-clinical-note-post.md Show Validation Information (0)


input/includes/diagnosticreport-quickstart.md Show Validation Information (0)


input/includes/diff-display-note.md Show Validation Information (0)


input/includes/docref.md Show Validation Information (0)


input/includes/docref-example1.md Show Validation Information (0)


input/includes/docref-example2.md Show Validation Information (0)


input/includes/documentreference-clinical-note-post.md Show Validation Information (0)


input/includes/documentreference-quickstart.md Show Validation Information (0)


input/includes/dstu2-r4-table2.md Show Validation Information (0)


input/includes/encounter-location.md Show Validation Information (0)


input/includes/example-list-generator.md Show Validation Information (0)


input/includes/example_link.md Show Validation Information (0)


input/includes/examplebutton.html Show Validation Information (0)


input/includes/examplebutton_default.html Show Validation Information (0)


input/includes/ext-list-generator.md Show Validation Information (0)


input/includes/get-all-active-meds.md Show Validation Information (0)


input/includes/get-all-active-meds-searchbundle.md Show Validation Information (0)


input/includes/get-all-allergy-provenance-future-health.md Show Validation Information (0)


input/includes/get-all-allergy-provenance-good-health.md Show Validation Information (0)


input/includes/get-all-allergy-provenance-sunshine-health.md Show Validation Information (0)


input/includes/get-all-ecounter-meds-searchbundle.md Show Validation Information (0)


input/includes/get-all-enc-meds.md Show Validation Information (0)


input/includes/get-all-meds.md Show Validation Information (0)


input/includes/get-all-meds-searchbundle.md Show Validation Information (0)


input/includes/granular-scopes-table.md Show Validation Information (0)


input/includes/img.html Show Validation Information (0)


input/includes/img-med.html Show Validation Information (0)


input/includes/img-narrow.html Show Validation Information (0)


input/includes/img-portrait.html Show Validation Information (0)


input/includes/img-portrait-med.html Show Validation Information (0)


input/includes/img-small.html Show Validation Information (0)


input/includes/link-list.md Show Validation Information (0)


input/includes/logo.md Show Validation Information (0)


input/includes/mcc-valueset-list-generator.html Show Validation Information (0)


input/includes/missing-status.md Show Validation Information (0)


input/includes/ms-target-table-generator.md Show Validation Information (0)


input/includes/new_page.md Show Validation Information (0)


input/includes/non-uscdi-profiles.md Show Validation Information (0)


input/includes/nonnormative-example-boilerplate.md Show Validation Information (0)


input/includes/note-and-report-types-scenario1.md Show Validation Information (0)


input/includes/note-and-report-types-scenario2.md Show Validation Information (0)


input/includes/note-and-report-types-scenario3.md Show Validation Information (0)


input/includes/note-and-report-types-scenario4.md Show Validation Information (0)


input/includes/obs_cat_guidance.md Show Validation Information (0)


input/includes/observation-quickstart1.md Show Validation Information (0)


input/includes/observation_guidance_1.md Show Validation Information (0)


input/includes/page-link-list.md Show Validation Information (0)


input/includes/prov-white-list.md Show Validation Information (0)


input/includes/provenance-author-bullet-generator.md Show Validation Information (0)


input/includes/provenance-source-table-generator.md Show Validation Information (0)


input/includes/questionnaireresponse-context-note.md Show Validation Information (0)


input/includes/quickstart-intro.md Show Validation Information (0)


input/includes/r4-link-list.md Show Validation Information (0)


input/includes/read-and-write-format-scenario1.md Show Validation Information (0)


input/includes/read-and-write-format-scenario2.md Show Validation Information (0)


input/includes/representing-meds.md Show Validation Information (0)


input/includes/res-list-generator.md Show Validation Information (0)


input/includes/resource-scopes-table.md Show Validation Information (0)


input/includes/schematron-list-generator.md Show Validation Information (0)


input/includes/sd-list-generator.md Show Validation Information (0)


input/includes/sd_link.html Show Validation Information (0)


input/includes/should-project-us.md Show Validation Information (0)


input/includes/specimen-include-note.md Show Validation Information (0)


input/includes/uscdi-uscore-map.html Show Validation Information (0)


input/includes/uscdi-uscore-version-table.md Show Validation Information (0)


input/includes/uscore_sp_list.md Show Validation Information (0)


input/includes/valueset-ref-all-table-generator.html Show Validation Information (0)


input/includes/vitals-guidance.md Show Validation Information (0)


input/includes/whats-new/v8.md Show Validation Information (0)


input/includes/whats-new/v8-ballot.md Show Validation Information (0)


input/includes/whats-new/v8.0.1.md Show Validation Information (0)


input/includes/write-and-docref.md Show Validation Information (0)


input/intro-notes Show Validation Information (0)


input/intro-notes/DiagnosticReport-cbc-intro.md Show Validation Information (0)


input/intro-notes/DiagnosticReport-cbc-intro.md Show Validation Information (0)


input/intro-notes/DiagnosticReport-metabolic-panel-intro.md Show Validation Information (0)


input/intro-notes/DiagnosticReport-metabolic-panel-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-erythrocytes-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-erythrocytes-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-hematocrit-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-hematocrit-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-hemoglobin-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-hemoglobin-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-leukocytes-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-leukocytes-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-mch-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-mch-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-mchc-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-mchc-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-mcv-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-mcv-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-platelets-intro.md Show Validation Information (0)


input/intro-notes/Observation-cbc-platelets-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-bun-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-bun-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-calcium-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-calcium-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-chloride-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-chloride-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-co2-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-co2-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-creatinine-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-creatinine-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-glucose-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-glucose-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-potassium-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-potassium-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-sodium-intro.md Show Validation Information (0)


input/intro-notes/Observation-serum-sodium-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-head-occipital-frontal-circumference-percentile-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-head-occipital-frontal-circumference-percentile-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-head-occipital-frontal-circumference-percentile-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-head-occipital-frontal-circumference-percentile-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-pediatric-bmi-for-age-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-pediatric-bmi-for-age-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-pediatric-bmi-for-age-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-pediatric-bmi-for-age-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-pediatric-weight-for-height-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-pediatric-weight-for-height-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-pediatric-weight-for-height-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-pediatric-weight-for-height-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-adi-documentreference-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-adi-documentreference-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-adi-documentreference-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-adi-documentreference-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-allergyintolerance-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-allergyintolerance-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-allergyintolerance-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-allergyintolerance-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-average-blood-pressure-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-average-blood-pressure-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-average-blood-pressure-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-average-blood-pressure-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-birthsex-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-birthsex-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-blood-pressure-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-blood-pressure-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-blood-pressure-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-blood-pressure-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-bmi-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-bmi-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-bmi-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-bmi-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-body-height-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-body-height-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-body-height-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-body-height-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-body-temperature-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-body-temperature-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-body-temperature-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-body-temperature-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-body-weight-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-body-weight-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-body-weight-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-body-weight-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-care-experience-preference-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-care-experience-preference-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-care-experience-preference-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-care-experience-preference-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-careplan-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-careplan-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-careplan-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-careplan-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-careteam-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-careteam-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-careteam-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-careteam-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-condition-encounter-diagnosis-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-condition-encounter-diagnosis-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-condition-encounter-diagnosis-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-condition-encounter-diagnosis-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-condition-problems-health-concerns-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-condition-problems-health-concerns-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-condition-problems-health-concerns-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-condition-problems-health-concerns-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-coverage-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-coverage-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-coverage-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-coverage-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-diagnosticreport-lab-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-diagnosticreport-lab-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-diagnosticreport-lab-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-diagnosticreport-lab-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-diagnosticreport-note-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-diagnosticreport-note-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-diagnosticreport-note-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-diagnosticreport-note-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-documentreference-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-documentreference-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-documentreference-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-documentreference-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-encounter-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-encounter-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-encounter-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-encounter-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-ethnicity-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-ethnicity-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-goal-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-goal-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-goal-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-goal-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-head-circumference-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-head-circumference-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-head-circumference-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-head-circumference-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-heart-rate-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-heart-rate-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-heart-rate-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-heart-rate-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-immunization-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-immunization-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-immunization-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-immunization-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-implantable-device-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-implantable-device-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-implantable-device-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-implantable-device-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-location-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-location-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-location-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-location-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-medication-adherence-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-medication-adherence-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-medication-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-medication-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-medication-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-medication-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-medicationdispense-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-medicationdispense-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-medicationdispense-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-medicationdispense-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-medicationrequest-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-medicationrequest-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-medicationrequest-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-medicationrequest-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-adi-documentation-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-adi-documentation-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-adi-documentation-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-adi-documentation-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-clinical-result-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-clinical-result-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-clinical-result-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-clinical-result-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-lab-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-lab-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-lab-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-lab-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-occupation-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-occupation-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-occupation-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-occupation-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-pregnancyintent-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-pregnancyintent-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-pregnancyintent-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-pregnancyintent-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-pregnancystatus-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-pregnancystatus-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-pregnancystatus-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-pregnancystatus-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-screening-assessment-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-screening-assessment-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-screening-assessment-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-screening-assessment-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-sexual-orientation-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-sexual-orientation-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-sexual-orientation-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-observation-sexual-orientation-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-organization-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-organization-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-organization-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-organization-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-patient-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-patient-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-patient-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-patient-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-practitioner-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-practitioner-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-practitioner-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-practitioner-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-practitionerrole-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-practitionerrole-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-practitionerrole-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-practitionerrole-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-procedure-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-procedure-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-procedure-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-procedure-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-provenance-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-provenance-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-provenance-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-provenance-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-pulse-oximetry-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-pulse-oximetry-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-pulse-oximetry-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-pulse-oximetry-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-questionnaireresponse-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-questionnaireresponse-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-questionnaireresponse-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-questionnaireresponse-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-race-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-race-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-relatedperson-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-relatedperson-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-relatedperson-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-relatedperson-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-respiratory-rate-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-respiratory-rate-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-respiratory-rate-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-respiratory-rate-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-servicerequest-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-servicerequest-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-servicerequest-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-servicerequest-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-sex-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-sex-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-simple-observation-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-simple-observation-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-simple-observation-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-simple-observation-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-smokingstatus-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-smokingstatus-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-smokingstatus-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-smokingstatus-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-specimen-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-specimen-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-specimen-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-specimen-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-treatment-intervention-preference-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-treatment-intervention-preference-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-treatment-intervention-preference-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-treatment-intervention-preference-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-tribal-affiliation-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-tribal-affiliation-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-vital-signs-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-vital-signs-intro.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-vital-signs-notes.md Show Validation Information (0)


input/intro-notes/StructureDefinition-us-core-vital-signs-notes.md Show Validation Information (0)


input/intro-notes/ValueSet-detailed-ethnicity-intro.md Show Validation Information (0)


input/intro-notes/ValueSet-detailed-ethnicity-intro.md Show Validation Information (0)


input/intro-notes/ValueSet-detailed-race-intro.md Show Validation Information (0)


input/intro-notes/ValueSet-detailed-race-intro.md Show Validation Information (0)


input/intro-notes/ValueSet-simple-language-intro.md Show Validation Information (0)


input/intro-notes/ValueSet-simple-language-intro.md Show Validation Information (0)


input/intro-notes/ValueSet-us-core-location-type-intro.md Show Validation Information (0)


input/intro-notes/ValueSet-us-core-location-type-intro.md Show Validation Information (0)


input/intro-notes/ValueSet-us-core-pregnancy-intent-intro.md Show Validation Information (0)


input/intro-notes/ValueSet-us-core-pregnancy-intent-intro.md Show Validation Information (0)


input/pagecontent Show Validation Information (0)


input/pagecontent/ImplementationGuide-hl7.fhir.us.core.md Show Validation Information (0)


input/pagecontent/ImplementationGuide-hl7.fhir.us.core.md Show Validation Information (0)


input/pagecontent/basic-provenance.md Show Validation Information (0)


input/pagecontent/basic-provenance.md Show Validation Information (0)


input/pagecontent/capability-statements.md Show Validation Information (0)


input/pagecontent/capability-statements.md Show Validation Information (0)


input/pagecontent/changes.md Show Validation Information (0)


input/pagecontent/changes.md Show Validation Information (0)


input/pagecontent/changes-between-versions.md Show Validation Information (0)


input/pagecontent/changes-between-versions.md Show Validation Information (0)


input/pagecontent/clinical-notes.md Show Validation Information (0)


input/pagecontent/clinical-notes.md Show Validation Information (0)


input/pagecontent/conformance.md Show Validation Information (0)


input/pagecontent/conformance.md Show Validation Information (0)


input/pagecontent/downloads.md Show Validation Information (0)


input/pagecontent/downloads.md Show Validation Information (0)


input/pagecontent/element-level-provenance.md Show Validation Information (0)


input/pagecontent/element-level-provenance.md Show Validation Information (0)


input/pagecontent/examples.md Show Validation Information (0)


input/pagecontent/examples.md Show Validation Information (0)


input/pagecontent/general-guidance.md Show Validation Information (0)


input/pagecontent/general-guidance.md Show Validation Information (0)


input/pagecontent/general-requirements.md Show Validation Information (0)


input/pagecontent/general-requirements.md Show Validation Information (0)


input/pagecontent/guidance.md Show Validation Information (0)


input/pagecontent/guidance.md Show Validation Information (0)


input/pagecontent/index.md Show Validation Information (0)


input/pagecontent/index.md Show Validation Information (0)


input/pagecontent/looking-ahead.md Show Validation Information (0)


input/pagecontent/looking-ahead.md Show Validation Information (0)


input/pagecontent/medication-list.md Show Validation Information (0)


input/pagecontent/medication-list.md Show Validation Information (0)


input/pagecontent/must-support.md Show Validation Information (0)


input/pagecontent/must-support.md Show Validation Information (0)


input/pagecontent/observation-summary.md Show Validation Information (0)


input/pagecontent/observation-summary.md Show Validation Information (0)


input/pagecontent/patient-data-feed.md Show Validation Information (0)


input/pagecontent/patient-data-feed.md Show Validation Information (0)


input/pagecontent/patient-data-feed-additional-resources.md Show Validation Information (0)


input/pagecontent/patient-data-feed-additional-resources.md Show Validation Information (0)


input/pagecontent/profiles-and-extensions.md Show Validation Information (0)


input/pagecontent/profiles-and-extensions.md Show Validation Information (0)


input/pagecontent/relationship-with-other-igs.md Show Validation Information (0)


input/pagecontent/relationship-with-other-igs.md Show Validation Information (0)


input/pagecontent/scopes.md Show Validation Information (0)


input/pagecontent/scopes.md Show Validation Information (0)


input/pagecontent/screening-and-assessments.md Show Validation Information (0)


input/pagecontent/screening-and-assessments.md Show Validation Information (0)


input/pagecontent/search-parameters-and-operations.md Show Validation Information (0)


input/pagecontent/search-parameters-and-operations.md Show Validation Information (0)


input/pagecontent/security.md Show Validation Information (0)


input/pagecontent/security.md Show Validation Information (0)


input/pagecontent/terminology.md Show Validation Information (0)


input/pagecontent/terminology.md Show Validation Information (0)


input/pagecontent/us-core-roadmap.md Show Validation Information (0)


input/pagecontent/us-core-roadmap.md Show Validation Information (0)


input/pagecontent/uscdi.md Show Validation Information (0)


input/pagecontent/uscdi.md Show Validation Information (0)


input/pagecontent/vsacname-fhiruri-map.md Show Validation Information (0)


input/pagecontent/vsacname-fhiruri-map.md Show Validation Information (0)


input/pagecontent/writing-vital-signs.md Show Validation Information (0)


input/pagecontent/writing-vital-signs.md Show Validation Information (0)


input/resources/CodeSystem-careplan-category.json Show Validation Information (1)


input/resources/CodeSystem-condition-category.json Show Validation Information (1)


input/resources/CodeSystem-us-core-category.json Show Validation Information (1)


input/resources/CodeSystem-us-core-documentreference-category.json Show Validation Information (1)


input/resources/CodeSystem-us-core-provenance-participant-type.json Show Validation Information (1)


input/resources/StructureDefinition-pediatric-bmi-for-age.json Show Validation Information (1)


input/resources/StructureDefinition-pediatric-weight-for-height.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-adi-documentreference.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-allergyintolerance.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-authentication-time.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-average-blood-pressure.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-birthsex.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-blood-pressure.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-bmi.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-body-height.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-body-temperature.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-body-weight.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-care-experience-preference.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-careplan.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-careteam.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-condition-encounter-diagnosis.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-condition-problems-health-concerns.json Show Validation Information (1)

PathSeverityMessageValidating
StructureDefinition​.snapshot​.element[16]​.type[0]​.profile[0] (l1​/c86861)warningThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate' to 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate|5.2.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition
StructureDefinition​.differential​.element[3]​.type[0]​.profile[0] (l1​/c132363)warningThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate' to 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate|5.2.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition

input/resources/StructureDefinition-us-core-coverage.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-diagnosticreport-lab.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-diagnosticreport-note.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-direct.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-documentreference.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-encounter.json Show Validation Information (1)

PathSeverityMessageValidating
StructureDefinition​.snapshot​.element[74]​.binding​.valueSet (l1​/c152770)warningThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0092'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology#5.5.0), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0092' to 'http://terminology.hl7.org/ValueSet/v2-0092|3.0.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition
StructureDefinition​.snapshot​.element[79]​.binding​.valueSet (l1​/c158227)warningThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.0.0', found versions: 3.0.0 (from hl7.terminology#5.5.0), 5.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition' to 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition|5.0.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition
StructureDefinition​.differential​.element[19]​.binding​.valueSet (l1​/c175317)warningThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.0.0', found versions: 3.0.0 (from hl7.terminology#5.5.0), 5.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition' to 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition|5.0.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition

input/resources/StructureDefinition-us-core-ethnicity.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-extension-questionnaire-uri.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-genderIdentity.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-goal.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-head-circumference.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-heart-rate.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-immunization.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-implantable-device.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-individual-sex.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-interpreter-needed.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-jurisdiction.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-location.json Show Validation Information (1)

PathSeverityMessageValidating
StructureDefinition​.snapshot​.element[11]​.binding​.valueSet (l1​/c57443)warningThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0116'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology#5.5.0), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0116' to 'http://terminology.hl7.org/ValueSet/v2-0116|3.0.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition

input/resources/StructureDefinition-us-core-medication.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-medication-adherence.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-medicationdispense.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-medicationrequest.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-observation-adi-documentation.json Show Validation Information (1)

PathSeverityMessageValidating
StructureDefinition​.snapshot​.element[8]​.type[0]​.profile[0] (l1​/c60107)warningThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo' to 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo|5.2.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition
StructureDefinition​.differential​.element[1]​.type[0]​.profile[0] (l1​/c131937)warningThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo' to 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo|5.2.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition

input/resources/StructureDefinition-us-core-observation-clinical-result.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-observation-lab.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-observation-occupation.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-observation-pregnancyintent.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-observation-pregnancystatus.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-observation-screening-assessment.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-observation-sexual-orientation.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-organization.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-practitioner.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-practitionerrole.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-procedure.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-provenance.json Show Validation Information (1)

PathSeverityMessageValidating
StructureDefinition​.snapshot​.element[20]​.binding​.valueSet (l1​/c80448)warningThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-PurposeOfUse'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.1.0', found versions: 3.0.0 (from hl7.terminology#5.5.0), 3.1.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-PurposeOfUse' to 'http://terminology.hl7.org/ValueSet/v3-PurposeOfUse|3.1.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition

input/resources/StructureDefinition-us-core-pulse-oximetry.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-questionnaireresponse.json Show Validation Information (1)

PathSeverityMessageValidating
StructureDefinition​.snapshot​.element[8]​.type[0]​.profile[0] (l1​/c68116)warningThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature' to 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature|5.2.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition
StructureDefinition​.snapshot​.element[9]​.type[0]​.profile[0] (l1​/c69088)warningThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-completionMode'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-completionMode' to 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-completionMode|5.2.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition
StructureDefinition​.snapshot​.element[17]​.type[0]​.profile[0] (l1​/c78774)warningThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/display'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/display' to 'http://hl7.org/fhir/StructureDefinition/display|5.2.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition
StructureDefinition​.snapshot​.element[30]​.type[0]​.profile[0] (l1​/c95280)warningThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature' to 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature|5.2.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition

input/resources/StructureDefinition-us-core-race.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-relatedperson.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-respiratory-rate.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-sex.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-simple-observation.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-smokingstatus.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-specimen.json Show Validation Information (1)

PathSeverityMessageValidating
StructureDefinition​.snapshot​.element[27]​.binding​.valueSet (l1​/c60656)warningThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0916'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology#5.5.0), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0916' to 'http://terminology.hl7.org/ValueSet/v2-0916|3.0.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition
StructureDefinition​.snapshot​.element[45]​.binding​.valueSet (l1​/c80246)warningThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0371'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology#5.5.0), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0371' to 'http://terminology.hl7.org/ValueSet/v2-0371|3.0.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSStructureDefinition

input/resources/StructureDefinition-us-core-treatment-intervention-preference.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-tribal-affiliation.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-uscdi-requirements.json Show Validation Information (1)


input/resources/StructureDefinition-us-core-vital-signs.json Show Validation Information (1)


input/resources/ValueSet-us-core-clinical-note-type.json Show Validation Information (1)


input/resources/ValueSet-us-core-clinical-result-observation-category.json Show Validation Information (1)

PathSeverityMessageValidating
ValueSet.compose.include[0]informationPinned the version of http://terminology.hl7.org/CodeSystem/observation-category to 2.0.0 from choices of 1.0.0 (hl7.terminology#5.5.0), 2.0.0 (hl7.terminology.r4#7.1.0) PIN_VERSION--

input/resources/ValueSet-us-core-condition-code-current.json Show Validation Information (1)


input/resources/ValueSet-us-core-diagnosticreport-category.json Show Validation Information (1)


input/resources/ValueSet-us-core-diagnosticreport-report-and-note-codes.json Show Validation Information (1)


input/resources/ValueSet-us-core-documentreference-category.json Show Validation Information (1)


input/resources/ValueSet-us-core-documentreference-type.json Show Validation Information (1)

PathSeverityMessageValidating
ValueSet.compose.include[0]informationPinned the version of http://terminology.hl7.org/CodeSystem/v3-NullFlavor to 4.0.0 from choices of 3.0.0 (hl7.terminology#5.5.0), 4.0.0 (hl7.terminology.r4#7.1.0) PIN_VERSION--

input/resources/ValueSet-us-core-narrative-status.json Show Validation Information (1)


input/resources/ValueSet-us-core-observation-smoking-status-status.json Show Validation Information (1)


input/resources/ValueSet-us-core-provenance-participant-type.json Show Validation Information (1)

PathSeverityMessageValidating
ValueSet.compose.include[1]informationPinned the version of http://terminology.hl7.org/CodeSystem/provenance-participant-type to 2.0.0 from choices of 1.0.0 (hl7.terminology#5.5.0), 2.0.0 (hl7.terminology.r4#7.1.0) PIN_VERSION--

input/resources/ValueSet-us-core-screening-assessment-condition-category.json Show Validation Information (1)


input/resources/ValueSet-us-core-screening-assessment-observation-category.json Show Validation Information (1)

PathSeverityMessageValidating
ValueSet.compose.include[1]informationPinned the version of http://terminology.hl7.org/CodeSystem/observation-category to 2.0.0 from choices of 1.0.0 (hl7.terminology#5.5.0), 2.0.0 (hl7.terminology.r4#7.1.0) PIN_VERSION--

input/resources/ValueSet-us-core-screening-assessment-observation-maximum-category.json Show Validation Information (1)

PathSeverityMessageValidating
ValueSet.compose.include[1]informationPinned the version of http://terminology.hl7.org/CodeSystem/observation-category to 2.0.0 from choices of 1.0.0 (hl7.terminology#5.5.0), 2.0.0 (hl7.terminology.r4#7.1.0) PIN_VERSION--
ValueSet.compose.exclude[0].systemwarningThere are multiple different potential matches for the url 'http://terminology.hl7.org/CodeSystem/observation-category'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '2.0.0', found versions: 1.0.0 (from hl7.terminology#5.5.0), 2.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/CodeSystem/observation-category' to 'http://terminology.hl7.org/CodeSystem/observation-category|2.0.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS--

input/resources/ValueSet-us-core-simple-observation-category.json Show Validation Information (1)

PathSeverityMessageValidating
ValueSet.compose.include[1]informationPinned the version of http://terminology.hl7.org/CodeSystem/observation-category to 2.0.0 from choices of 1.0.0 (hl7.terminology#5.5.0), 2.0.0 (hl7.terminology.r4#7.1.0) PIN_VERSION--

input/resources/ValueSet-us-core-specimen-condition.json Show Validation Information (1)

PathSeverityMessageValidating
ValueSet​.compose​.include[0]​.valueSet[0] (l1​/c2419)warningThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0493'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology#5.5.0), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0493' to 'http://terminology.hl7.org/ValueSet/v2-0493|3.0.0' TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONSValueSet

input/resources/capabilitystatement-us-core-client.json Show Validation Information (1)


input/resources/capabilitystatement-us-core-server.json Show Validation Information (1)


input/resources/operationdefinition-docref.json Show Validation Information (1)


input/resources/searchparameter-us-core-allergyintolerance-clinical-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-allergyintolerance-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-careplan-category.json Show Validation Information (1)


input/resources/searchparameter-us-core-careplan-date.json Show Validation Information (1)


input/resources/searchparameter-us-core-careplan-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-careplan-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-careteam-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-careteam-role.json Show Validation Information (1)


input/resources/searchparameter-us-core-careteam-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-condition-abatement-date.json Show Validation Information (1)


input/resources/searchparameter-us-core-condition-asserted-date.json Show Validation Information (1)


input/resources/searchparameter-us-core-condition-category.json Show Validation Information (1)


input/resources/searchparameter-us-core-condition-clinical-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-condition-code.json Show Validation Information (1)


input/resources/searchparameter-us-core-condition-encounter.json Show Validation Information (1)


input/resources/searchparameter-us-core-condition-lastUpdated.json Show Validation Information (1)


input/resources/searchparameter-us-core-condition-onset-date.json Show Validation Information (1)


input/resources/searchparameter-us-core-condition-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-condition-recorded-date.json Show Validation Information (1)


input/resources/searchparameter-us-core-coverage-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-device-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-device-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-device-type.json Show Validation Information (1)


input/resources/searchparameter-us-core-diagnosticreport-category.json Show Validation Information (1)


input/resources/searchparameter-us-core-diagnosticreport-code.json Show Validation Information (1)


input/resources/searchparameter-us-core-diagnosticreport-date.json Show Validation Information (1)


input/resources/searchparameter-us-core-diagnosticreport-lastUpdated.json Show Validation Information (1)


input/resources/searchparameter-us-core-diagnosticreport-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-diagnosticreport-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-documentreference-category.json Show Validation Information (1)


input/resources/searchparameter-us-core-documentreference-date.json Show Validation Information (1)


input/resources/searchparameter-us-core-documentreference-id.json Show Validation Information (1)


input/resources/searchparameter-us-core-documentreference-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-documentreference-period.json Show Validation Information (1)


input/resources/searchparameter-us-core-documentreference-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-documentreference-type.json Show Validation Information (1)


input/resources/searchparameter-us-core-encounter-class.json Show Validation Information (1)


input/resources/searchparameter-us-core-encounter-date.json Show Validation Information (1)


input/resources/searchparameter-us-core-encounter-discharge-disposition.json Show Validation Information (1)


input/resources/searchparameter-us-core-encounter-id.json Show Validation Information (1)


input/resources/searchparameter-us-core-encounter-identifier.json Show Validation Information (1)


input/resources/searchparameter-us-core-encounter-lastUpdated.json Show Validation Information (1)


input/resources/searchparameter-us-core-encounter-location.json Show Validation Information (1)


input/resources/searchparameter-us-core-encounter-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-encounter-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-encounter-type.json Show Validation Information (1)


input/resources/searchparameter-us-core-ethnicity.json Show Validation Information (1)


input/resources/searchparameter-us-core-goal-description.json Show Validation Information (1)


input/resources/searchparameter-us-core-goal-lifecycle-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-goal-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-goal-target-date.json Show Validation Information (1)


input/resources/searchparameter-us-core-immunization-date.json Show Validation Information (1)


input/resources/searchparameter-us-core-immunization-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-immunization-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-location-address.json Show Validation Information (1)


input/resources/searchparameter-us-core-location-address-city.json Show Validation Information (1)


input/resources/searchparameter-us-core-location-address-postalcode.json Show Validation Information (1)


input/resources/searchparameter-us-core-location-address-state.json Show Validation Information (1)


input/resources/searchparameter-us-core-location-name.json Show Validation Information (1)


input/resources/searchparameter-us-core-medicationdispense-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-medicationdispense-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-medicationdispense-type.json Show Validation Information (1)


input/resources/searchparameter-us-core-medicationrequest-authoredon.json Show Validation Information (1)


input/resources/searchparameter-us-core-medicationrequest-encounter.json Show Validation Information (1)


input/resources/searchparameter-us-core-medicationrequest-intent.json Show Validation Information (1)


input/resources/searchparameter-us-core-medicationrequest-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-medicationrequest-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-observation-category.json Show Validation Information (1)


input/resources/searchparameter-us-core-observation-code.json Show Validation Information (1)


input/resources/searchparameter-us-core-observation-date.json Show Validation Information (1)


input/resources/searchparameter-us-core-observation-lastUpdated.json Show Validation Information (1)


input/resources/searchparameter-us-core-observation-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-observation-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-organization-address.json Show Validation Information (1)


input/resources/searchparameter-us-core-organization-name.json Show Validation Information (1)


input/resources/searchparameter-us-core-patient-birthdate.json Show Validation Information (1)


input/resources/searchparameter-us-core-patient-death-date.json Show Validation Information (1)


input/resources/searchparameter-us-core-patient-family.json Show Validation Information (1)


input/resources/searchparameter-us-core-patient-given.json Show Validation Information (1)


input/resources/searchparameter-us-core-patient-id.json Show Validation Information (1)


input/resources/searchparameter-us-core-patient-identifier.json Show Validation Information (1)


input/resources/searchparameter-us-core-patient-name.json Show Validation Information (1)


input/resources/searchparameter-us-core-practitioner-id.json Show Validation Information (1)


input/resources/searchparameter-us-core-practitioner-identifier.json Show Validation Information (1)


input/resources/searchparameter-us-core-practitioner-name.json Show Validation Information (1)


input/resources/searchparameter-us-core-practitionerrole-practitioner.json Show Validation Information (1)


input/resources/searchparameter-us-core-practitionerrole-specialty.json Show Validation Information (1)


input/resources/searchparameter-us-core-procedure-code.json Show Validation Information (1)


input/resources/searchparameter-us-core-procedure-date.json Show Validation Information (1)


input/resources/searchparameter-us-core-procedure-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-procedure-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-questionnaireresponse-authored.json Show Validation Information (1)


input/resources/searchparameter-us-core-questionnaireresponse-id.json Show Validation Information (1)


input/resources/searchparameter-us-core-questionnaireresponse-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-questionnaireresponse-questionnaire.json Show Validation Information (1)


input/resources/searchparameter-us-core-questionnaireresponse-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-race.json Show Validation Information (1)


input/resources/searchparameter-us-core-relatedperson-id.json Show Validation Information (1)


input/resources/searchparameter-us-core-relatedperson-name.json Show Validation Information (1)


input/resources/searchparameter-us-core-relatedperson-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-servicerequest-authored.json Show Validation Information (1)


input/resources/searchparameter-us-core-servicerequest-category.json Show Validation Information (1)


input/resources/searchparameter-us-core-servicerequest-code.json Show Validation Information (1)


input/resources/searchparameter-us-core-servicerequest-id.json Show Validation Information (1)


input/resources/searchparameter-us-core-servicerequest-patient.json Show Validation Information (1)


input/resources/searchparameter-us-core-servicerequest-status.json Show Validation Information (1)


input/resources/searchparameter-us-core-specimen-id.json Show Validation Information (1)


input/resources/searchparameter-us-core-specimen-patient.json Show Validation Information (1)


input/resources/structuredefinition-head-occipital-frontal-circumference-percentile.json Show Validation Information (1)


input/resources/structuredefinition-us-core-patient.json Show Validation Information (1)


input/resources/structuredefinition-us-core-servicerequest.json Show Validation Information (1)


input/resources/valueset-us-core-condition-code.json Show Validation Information (1)


input/resources/valueset-us-core-goal-description.json Show Validation Information (1)

PathSeverityMessageValidating
ValueSet​.where(id = 'us-core-goal-description')warningError from https://tx.fhir.org/r4: Error: The code System "http://snomed.info/sct" has a grammar, and cannot be enumerated directly (from server, see log) --

input/resources/valueset-us-core-laboratory-test-codes.json Show Validation Information (1)


input/resources/valueset-us-core-problem-or-health-concern.json Show Validation Information (1)

PathSeverityMessageValidating
ValueSet.compose.include[0]informationPinned the version of http://terminology.hl7.org/CodeSystem/condition-category to 2.0.0 from choices of 1.0.0 (hl7.terminology#5.5.0), 2.0.0 (hl7.terminology.r4#7.1.0) PIN_VERSION--

input/resources/valueset-us-core-procedure-code.json Show Validation Information (1)

PathSeverityMessageValidating
ValueSet​.where(id = 'us-core-procedure-code')warningError from https://tx.fhir.org/r4: Error: The code System "http://www.ama-assn.org/go/cpt" has a grammar, and cannot be enumerated directly (from server, see log) --

input/resources/valueset-us-core-servicerequest-category.json Show Validation Information (1)


temp/pages/_includes/artifacts.xml Show Validation Information (0)


template/config Show Validation Information (0)


template/config/_config.yml Show Validation Information (0)

Suppressed Messages (Warnings, hints, broken links)

04. === Several examples derived from this profile are provided in this guide (1) ===

05. === These questionnaires are created using NLM tooling based on LOINC LFORMs. They use standard FHIR Questionnaire Extensions that "extend" the base SDC profile ===

06. === The code is from the US Core defined NUCC binding and not from the base FHIR preferred c80-practice-codes value set (updated text from 7.0.0) ===

07. === Examples provided in Bundle (e.g. PractitionerRole_Practitioner_Endpoint_Bundle_Example, Allergyintolerance Provenance Example) (2)===

08. === The following content is inherited from the base standard and cannot be changed ===

09. === The pattern is set in a repeating slice. The pattern is expected to hold for all repetitions of that slice. (It's fixing the 'system' for the identifier.) ===

10. === The self-link for these searchset bundles is to the $docref operation and not to a FHIR search string====

11. === Using the extension US Core Extension Questionnaire URI pointing to a PDF form of the Questionnaire for this example. Regarding the message: "No questionnaire is identified, so no validation can be performed against the base questionnaire" ===

15. === This Search Parameter expression `Goal.target.due as date` is inherited from the FHIR base. Since US Core inherits from the FHIR R4 base, this warning is acknowledged as an issue with the base specification. In R5, this expression has been updated to `(Goal.target.due.ofType(date))`. ===

17. === The 'no-narrative' parameter is used for these resource instances because they are displayed as inline JSON examples to illustrate transactions and the narrative elements degrades the human readability of the JSON ===

18. === The following code system and value set are in FHIR Core/THO and not under the direct control of US Core editors ===

19. === The following code systems are not discoverable because they are code systems in THO, but THO doesn't define the codes. They have been checked, and the identifiers are correct (updated text from 7.0.0) ===========

21. === The following code system is not discoverable because it is a code system in THO; however, THO doesn't define the codes due to AHA NUBC Patient Discharge Status Codes IP issues. These codes were checked manually (updated text from 7.0.0) ===

22. === FHIR R4 http://hl7.org/fhir/ValueSet/formatcodes is in error, which has been corrected in the FHIR R5. The guide is referencing the "HL7 ValueSet of Format Codes for use with Document Sharing" that is used in R5 (updated text from 7.0.0) ===

23. === The US Core Team is aware of this and is actively moving its value sets to VSAC and code systems to THO in each publication cycle. See the change log for details. ===

24. === These values are indeed large, and the ig-publisher informs the reader when the expansion is incomplete. ===

26. === Using the standard CapabilityStatementExpectation extension in additional contexts to fully express intended capabilities: see FHIR-12419 (115) (updated text from 7.0.0-ballot) ===

27. === These Examples demonstrate the use of additional Codes or Identifiers not defined in US Core profiles (Updated from 8.0.0) ===

28. === In this example, representing the concept clearly with human-readable annotations {pack-years} is not misleading. It clearly illustrates how to use the Observation with the code and demonstrates that a clinical need outweighs concerns about using annotations. ===

29. === US Core thoroughly documents its Must Support expectations for the must supports on the Must Support page, including how they apply to the choice of target references in the Must Support - Resource References section. (Also, see this chat https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Must.20Support.20Target.20Error.20for.20Reference.20type.20Element ===

30. === Two Bundle examples use this profile and one non-validated inline example that conforms to it as well - when the publisher understands versioned examples, we will create a published example to replace it. ===

31. === The binding applies to the Quantity data type for the US Core Vitals Signs Profile. It inherits the structure from Core, and a change request to correct this has been applied to the base FHIR ver 4.3.0 ("Release 4B"). Will need to slice value[x] in future (updated text from 7.0.0) ===

33. === To comply with Executive Order 14168, the following changes were made: 1)Removed USCDI mapping, guidance, and examples for the US Core Observation Sexual Orientation Profile 2) Removed the US Core Birth Sex Extension, guidance, and examples from the US Core Patient Profile 3) Deprecated the US Core Gender Identity and US Core Sex Extensions and removed them from the US Core Profile, USCDI mapping, guidance, and examples. Although the profiles and extensions will remain in this version of US Core to ensure backward compatibility, no examples will be provided. ===

34. === US Core provides IG-specific guidance on interpreting Must Support for slices at `~/must-support.html#must-support---slices`. Where we state: "...the slicer's Must Support property only defines the element level Must Support/Additional USCDI property. In other words, the slicer's Must Support/Additional USCDI is not inherited by the slices, and each slice must be explicitly tagged with the Must Support/Additional USCDI property to define that slice's conformance strength. If no Must Support/Additional USCDI property is defined for the slice, this lengthy chat: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Slices.20not.20inheriting.20preferred.20bindings.20from.20root/with/514257770 and the resulting tracker FHIR-50391. ===

35. === These messages have been acknowledged for this release. After reviewing the implications for conformant systems and downstream publications, we will consider updating and/or adopting the recommended replacement in a future release. ===

36. === These Extension StructureDefinitions were examined, and there are no substantive changes between versions and thus no reason to specify a version ===

37. === The following Extensions are in SDC, a dependent IG, or the FHIR R4 specification and not under the direct control of US Core editors ===

38. === The differences between these code system adn value set versions have been evaluated, and there are no differences or there are non-breaking changes (forward compatible)

40 === Similar to the base FHIR specification, the guide states in the introductory paragraph of the Conformance section's General Requirements page, "The conformance verbs - SHALL, SHOULD, MAY - used in this guide are defined in FHIR Conformance Rules, and these conventions are strictly adhered to throughout the guide. ===

43. === We are aware that this code system is a fragment. The error is due to an issue with the terminology server, not the implementation guide. For details, see the Zulip chat at: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/whither.20ICD9cm.20in.20THO.207.2E0.2E0.3F/with/559122224 ===

44 === This error will be present until the publication team can address it. See this Zulip chat: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Publisher.20v2.2E0.2E24.20-.20error.20in.20local.20build/with/547712458 ===

Errors sorted by type


Display_Name_for__should_be_one_of__instead_of

input/examples/Questionnaire-hunger-vital-sign-example.jsonWrong Display Name 'Hunger Vital Sign [HVS]' for http://loinc.org#88121-9. Valid display is one of 2 choices: 'Children's HealthWatch Hunger Vital Sign [HVS]' (en-US) or 'Children's HealthWatch Hunger Vital Sign [HVS]' (en-US) (for the language(s) 'en-US')SDCBaseQuestionnaire

IG_DEPENDENCY_VERSION_WARNING_OLD

fsh-generated/resources/ImplementationGuide-hl7.fhir.us.core.jsonThe ImplementationGuide uses package hl7.fhir.uv.sdc#3.0.0 released on 2022-03-08, but the most recent appropriate version is 4.0.0. This reference is getting old and the more recent version should be considered--

PIN_VERSION

input/resources/ValueSet-us-core-clinical-result-observation-category.jsonPinned the version of http://terminology.hl7.org/CodeSystem/observation-category to 2.0.0 from choices of 1.0.0 (hl7.terminology#5.5.0), 2.0.0 (hl7.terminology.r4#7.1.0)--
input/resources/ValueSet-us-core-documentreference-type.jsonPinned the version of http://terminology.hl7.org/CodeSystem/v3-NullFlavor to 4.0.0 from choices of 3.0.0 (hl7.terminology#5.5.0), 4.0.0 (hl7.terminology.r4#7.1.0)--
input/resources/ValueSet-us-core-provenance-participant-type.jsonPinned the version of http://terminology.hl7.org/CodeSystem/provenance-participant-type to 2.0.0 from choices of 1.0.0 (hl7.terminology#5.5.0), 2.0.0 (hl7.terminology.r4#7.1.0)--
input/resources/ValueSet-us-core-screening-assessment-observation-category.jsonPinned the version of http://terminology.hl7.org/CodeSystem/observation-category to 2.0.0 from choices of 1.0.0 (hl7.terminology#5.5.0), 2.0.0 (hl7.terminology.r4#7.1.0)--
input/resources/ValueSet-us-core-screening-assessment-observation-maximum-category.jsonPinned the version of http://terminology.hl7.org/CodeSystem/observation-category to 2.0.0 from choices of 1.0.0 (hl7.terminology#5.5.0), 2.0.0 (hl7.terminology.r4#7.1.0)--
input/resources/ValueSet-us-core-simple-observation-category.jsonPinned the version of http://terminology.hl7.org/CodeSystem/observation-category to 2.0.0 from choices of 1.0.0 (hl7.terminology#5.5.0), 2.0.0 (hl7.terminology.r4#7.1.0)--
input/resources/valueset-us-core-problem-or-health-concern.jsonPinned the version of http://terminology.hl7.org/CodeSystem/condition-category to 2.0.0 from choices of 1.0.0 (hl7.terminology#5.5.0), 2.0.0 (hl7.terminology.r4#7.1.0)--

TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS

input/resources/StructureDefinition-us-core-condition-problems-health-concerns.jsonThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate' to 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate|5.2.0'StructureDefinition
input/resources/StructureDefinition-us-core-condition-problems-health-concerns.jsonThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate' to 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate|5.2.0'StructureDefinition
input/resources/StructureDefinition-us-core-encounter.jsonThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0092'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology#5.5.0), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0092' to 'http://terminology.hl7.org/ValueSet/v2-0092|3.0.0'StructureDefinition
input/resources/StructureDefinition-us-core-encounter.jsonThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.0.0', found versions: 3.0.0 (from hl7.terminology#5.5.0), 5.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition' to 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition|5.0.0'StructureDefinition
input/resources/StructureDefinition-us-core-encounter.jsonThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.0.0', found versions: 3.0.0 (from hl7.terminology#5.5.0), 5.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition' to 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition|5.0.0'StructureDefinition
input/resources/StructureDefinition-us-core-location.jsonThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0116'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology#5.5.0), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0116' to 'http://terminology.hl7.org/ValueSet/v2-0116|3.0.0'StructureDefinition
input/resources/StructureDefinition-us-core-observation-adi-documentation.jsonThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo' to 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo|5.2.0'StructureDefinition
input/resources/StructureDefinition-us-core-observation-adi-documentation.jsonThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo' to 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo|5.2.0'StructureDefinition
input/resources/StructureDefinition-us-core-provenance.jsonThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-PurposeOfUse'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.1.0', found versions: 3.0.0 (from hl7.terminology#5.5.0), 3.1.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-PurposeOfUse' to 'http://terminology.hl7.org/ValueSet/v3-PurposeOfUse|3.1.0'StructureDefinition
input/resources/StructureDefinition-us-core-questionnaireresponse.jsonThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature' to 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature|5.2.0'StructureDefinition
input/resources/StructureDefinition-us-core-questionnaireresponse.jsonThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-completionMode'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-completionMode' to 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-completionMode|5.2.0'StructureDefinition
input/resources/StructureDefinition-us-core-questionnaireresponse.jsonThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/display'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/display' to 'http://hl7.org/fhir/StructureDefinition/display|5.2.0'StructureDefinition
input/resources/StructureDefinition-us-core-questionnaireresponse.jsonThere are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0-cibuild (from hl7.fhir.uv.extensions.r4#5.1.0-snapshot1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature' to 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature|5.2.0'StructureDefinition
input/resources/StructureDefinition-us-core-specimen.jsonThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0916'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology#5.5.0), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0916' to 'http://terminology.hl7.org/ValueSet/v2-0916|3.0.0'StructureDefinition
input/resources/StructureDefinition-us-core-specimen.jsonThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0371'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology#5.5.0), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0371' to 'http://terminology.hl7.org/ValueSet/v2-0371|3.0.0'StructureDefinition
input/resources/ValueSet-us-core-screening-assessment-observation-maximum-category.jsonThere are multiple different potential matches for the url 'http://terminology.hl7.org/CodeSystem/observation-category'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '2.0.0', found versions: 1.0.0 (from hl7.terminology#5.5.0), 2.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/CodeSystem/observation-category' to 'http://terminology.hl7.org/CodeSystem/observation-category|2.0.0'--
input/resources/ValueSet-us-core-specimen-condition.jsonThere are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0493'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology#5.5.0), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0493' to 'http://terminology.hl7.org/ValueSet/v2-0493|3.0.0'ValueSet

Terminology_TX_NoValid_3_CC

input/examples/AHC-HRSN-item-example-68517-2.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-10-minute-apgar-color.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#32401-2)US Core Observation Screening Assessment Profile
input/examples/Observation-10-minute-apgar-heart-rate.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#32402-0)US Core Observation Screening Assessment Profile
input/examples/Observation-10-minute-apgar-muscle-tone.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#32403-8)US Core Observation Screening Assessment Profile
input/examples/Observation-10-minute-apgar-reflex-irritability.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#32404-6)US Core Observation Screening Assessment Profile
input/examples/Observation-10-minute-apgar-respiratory-effort.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#32405-3)US Core Observation Screening Assessment Profile
input/examples/Observation-10-minute-apgar-score.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#9271-8)US Core Observation Screening Assessment Profile
input/examples/Observation-AUDIT-C-item-example-68519-8.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#68519-8)US Core Observation Screening Assessment Profile
input/examples/Observation-AUDIT-C-item-example-68520-6.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#68520-6)US Core Observation Screening Assessment Profile
input/examples/Observation-HVS-item-example-88122-7.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-HVS-item-example-88123-5.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-HVS-item-example-88124-3.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-HVS-panel-example-88121-9.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PHQ9-item-example-44250-9.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status)US Core Observation Screening Assessment Profile
input/examples/Observation-PHQ9-item-example-44251-7.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status)US Core Observation Screening Assessment Profile
input/examples/Observation-PHQ9-item-example-44252-5.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status)US Core Observation Screening Assessment Profile
input/examples/Observation-PHQ9-item-example-44253-3.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status)US Core Observation Screening Assessment Profile
input/examples/Observation-PHQ9-item-example-44254-1.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status)US Core Observation Screening Assessment Profile
input/examples/Observation-PHQ9-item-example-44255-8.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status)US Core Observation Screening Assessment Profile
input/examples/Observation-PHQ9-item-example-44258-2.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status)US Core Observation Screening Assessment Profile
input/examples/Observation-PHQ9-item-example-44259-0.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status)US Core Observation Screening Assessment Profile
input/examples/Observation-PHQ9-item-example-44260-8.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status)US Core Observation Screening Assessment Profile
input/examples/Observation-PHQ9-item-example-44261-6.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status)US Core Observation Screening Assessment Profile
input/examples/Observation-PHQ9-item-example-69722-7.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status)US Core Observation Screening Assessment Profile
input/examples/Observation-PHQ9-panel-example-44249-1.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#disability-status)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-54899-0.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-54899-0.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#54899-0)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-56051-6.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-56051-6.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#56051-6)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-56799-0.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-56799-0.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#56799-0)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-63512-8.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-63512-8.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#63512-8)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-63586-2.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-63586-2.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#63586-2)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-67875-5.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-67875-5.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#67875-5)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-71802-3.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-76437-3.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-76437-3.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#76437-3)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-76501-6.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-82589-3.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-82589-3.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#82589-3)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-93026-3.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-93027-1.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-93028-9.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-93029-7.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-93030-5.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-93033-9.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-93034-7.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-93035-4.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-93038-8.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-item-example-93038-8.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#93038-8)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-multiselect-item-example-32624-9-answer0.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-multiselect-item-example-32624-9-answer0.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#32624-9)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-multiselect-item-example-32624-9-answer1.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-multiselect-item-example-32624-9-answer1.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#32624-9)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-multiselect-item-example-93031-3-answer0.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-multiselect-item-example-93031-3-answer1.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-panel-example-93025-5.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-panel-example-93039-6.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-panel-example-93040-4.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-panel-example-93041-2.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-panel-example-93042-0.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-PRAPARE-panel-example-93043-8.jsonNone of the codings provided are in the value set 'Observation Category Codes' (http://hl7.org/fhir/ValueSet/observation-category|4.0.1), and a coding is recommended to come from this value set (codes = http://hl7.org/fhir/us/core/CodeSystem/us-core-category#sdoh)US Core Observation Screening Assessment Profile
input/examples/Observation-TAPS-item-example-96842-0.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#96842-0)US Core Observation Screening Assessment Profile
input/examples/Observation-TAPS-item-example-96843-8.jsonNone of the codings provided are in the value set 'Screening and Assessment Survey Codes' (http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610), and a coding is recommended to come from this value set (codes = http://loinc.org#96843-8)US Core Observation Screening Assessment Profile
input/examples/Observation-simple-observation-sdoh.jsonNone of the codings provided are in the value set 'LOINC Codes' (http://hl7.org/fhir/ValueSet/observation-codes|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#160695008)US Core Simple Observation Profile
input/examples/Observation-substance-use-status.jsonNone of the codings provided are in the value set 'LOINC Codes' (http://hl7.org/fhir/ValueSet/observation-codes|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#228366006)US Core Simple Observation Profile
input/examples/encounter-1036.jsonNone of the codings provided are in the value set 'USEncounterDischargeDisposition' (http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition|5.0.0), and a coding is recommended to come from this value set (codes = http://terminology.hl7.org/CodeSystem/nubc-UB92#01)US Core Encounter Profile

UNKNOWN_CODESYSTEM_VERSION

input/examples/medicationdispense-example.jsonA definition for CodeSystem 'http://www.nlm.nih.gov/research/umls/rxnorm' version '09022025' could not be found, so the code cannot be validated. Valid versions: 03022026US Core MedicationDispense Profile
input/examples/medicationrequest-coded-oral-axid.jsonA definition for CodeSystem 'http://www.nlm.nih.gov/research/umls/rxnorm' version '09022025' could not be found, so the code cannot be validated. Valid versions: 03022026US Core MedicationRequest Profile
input/examples/medicationrequest-self-tylenol.jsonA definition for CodeSystem 'http://www.nlm.nih.gov/research/umls/rxnorm' version '09022025' could not be found, so the code cannot be validated. Valid versions: 03022026US Core MedicationRequest Profile
input/examples/uscore-med1.jsonA definition for CodeSystem 'http://www.nlm.nih.gov/research/umls/rxnorm' version '09022025' could not be found, so the code cannot be validated. Valid versions: 03022026US Core Medication Profile
input/examples/uscore-med2.jsonA definition for CodeSystem 'http://www.nlm.nih.gov/research/umls/rxnorm' version '09022025' could not be found, so the code cannot be validated. Valid versions: 03022026US Core Medication Profile