Validation Results for DAPL

Generated Fri May 08 05:06:32 AEST 2026, FHIR version 4.0.1 for hl7.fhir.us.dapl#1.0.0-ballot (canonical = http://hl7.org/fhir/us/dapl (history)). See Full QA Report & IP

Quality Checks
Publisher Version:	IG Publisher Version: v2.2.7
Publication Code:	dapl . PackageId = hl7.fhir.us.dapl, Canonical = http://hl7.org/fhir/us/dapl
Realm Check for US:	Snomed: The IG specifies the US edition of SNOMED CT ✓ 15 Profiles not based on US Core
Language Info:	This IG has no language information
Publication Request:	package-id hl7.fhir.us.dapl version 1.0.0-ballot path http://hl7.org/fhir/us/dapl/2026May Pub-Mode working release status ballot Release-Label STU 1 Ballot Sequence (Group) STU 1 desc This is the STU 1 - Ballot version of the De-identification and Anonymization Profiles Library (DAPL) FHIR IG. changes changes.html first true category Privacy / Security title De-identified, Anonymized FHIR Profiles Library (DAPL) IG introduction De-identified, Anonymized Profiles Library (DAPL) FHIR IG defines a set of FHIR profiles to represent de-identified and anonymized data. ci-build https://build.fhir.org/ig/HL7/fhir-dapl RelatedIgs (None Found) This IG has never been published Proposed path for this publication should usually be the canonical with the version or sequence appended and then some kind of label (typically '-snapshot')
Supressed Messages:	23 Suppressed Issues
Dependency Checks:	Package Version FHIR Canonical Web Base Comment hl7.fhir.us.dapl 1.0.0-ballot R4 http://hl7.org/fhir/us/dapl hl7.terminology.r4 7.1.0 M R4 http://terminology.hl7.org http://terminology.hl7.org/7.1.0 hl7.fhir.uv.extensions.r4 5.2.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 hl7.fhir.uv.extensions.r4 5.2.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 (as above) hl7.fhir.us.core 8.0.1 M R4 http://hl7.org/fhir/us/core http://hl7.org/fhir/us/core/STU8.0.1 hl7.terminology.r4 7.0.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/7.0.0 Latest Release is 7.1.0 hl7.fhir.uv.extensions.r4 5.2.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 (as above) hl7.fhir.uv.smart-app-launch 2.2.0 M R4 http://hl7.org/fhir/smart-app-launch http://hl7.org/fhir/smart-app-launch/STU2.2 hl7.fhir.uv.extensions 5.1.0-snapshot1 O R5 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.1.0-snapshot1 FHIR Version Mismatch. Latest Release is 5.2.0 hl7.terminology.r5 5.3.0 O R5 http://terminology.hl7.org http://terminology.hl7.org/5.3.0 FHIR Version Mismatch. Latest Release is 7.1.0 hl7.terminology 5.5.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/5.5.0 Latest Release is 7.1.0 hl7.fhir.uv.extensions.r4 1.0.0 O R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/1.0.0 Latest Release is 5.2.0 us.nlm.vsac 0.24.0 M R4 http://fhir.org/packages/us.nlm.vsac http://fhir.org/packages/us.nlm.vsac hl7.fhir.uv.sdc 3.0.0 O R4 http://hl7.org/fhir/uv/sdc http://hl7.org/fhir/uv/sdc/STU3 Latest Release is 4.0.0 hl7.fhir.r4.examples 4.0.1 O R4 http://hl7.org/fhir http://hl7.org/fhir/R4 Latest Release is 5.0.0 us.cdc.phinvads 0.12.0 M R4 http://fhir.org/packages/us.cdc.phinvads http://fhir.org/packages/us.cdc.phinvads hl7.fhir.uv.extensions.r4 5.2.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 (as above) us.nlm.vsac 0.24.0 M R4 http://fhir.org/packages/us.nlm.vsac http://fhir.org/packages/us.nlm.vsac (as above) hl7.fhir.uv.tools.r4 1.1.2 M R4 http://hl7.org/fhir/tools http://hl7.org/fhir/tools/1.1.2 Internal 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:	no Non-HL7 references found
R5 Dependencies:	(none)
Draft Dependencies:	hl7.fhir.r4.core#4.0.1: GuideParameterCode (15 uses), CommonLanguages (19 uses), CarePlan (7 uses), DeviceRequest (3 uses), ImmunizationRecommendation (4 uses), MedicationRequest (8 uses), NutritionOrder (3 uses), ServiceRequest (11 uses), MedicationAdministration (6 uses), MedicationDispense (4 uses), MedicationStatement (6 uses), Procedure (9 uses), Immunization (7 uses), ImagingStudy (6 uses), LOINCCodes (6 uses), Practitioner (23 uses), PractitionerRole (23 uses), Organization (27 uses), CareTeam (5 uses), RelatedPerson (22 uses), SNOMEDCTBodyStructures (6 uses), ObservationMethods (3 uses), Specimen (4 uses), Device (13 uses), DeviceMetric (3 uses), ObservationReferenceRangeMeaningCodes (3 uses), ObservationReferenceRangeAppliesToCodes (3 uses), QuestionnaireResponse (6 uses), MolecularSequence (6 uses), DocumentReference (8 uses), Media (4 uses), Coverage (3 uses), FinancialResourceStatusCodes (1 uses), CoverageTypeAndSelf-PayCodes (1 uses), SubscriberRelationshipCodes (1 uses), CoverageClassCodes (1 uses), CoverageCopayTypeCodes (1 uses), ExampleCoverageFinancialExceptionCodes (1 uses), Contract (1 uses), AdverseEvent (1 uses), AdverseEventActuality (1 uses), AdverseEventCategory (1 uses), SNOMEDCTClinicalFindings (1 uses), Encounter (7 uses), Condition (14 uses), Location (9 uses), AdverseEventSeriousness (1 uses), AdverseEventSeverity (1 uses), AdverseEventOutcome (1 uses), Substance (2 uses), Medication (4 uses), AdverseEventCausalityAssessment (1 uses), AdverseEventCausalityMethod (1 uses), AllergyIntolerance (4 uses), FamilyMemberHistory (1 uses), ResearchStudy (1 uses), AllergyIntoleranceClinicalStatusCodes (1 uses), AllergyIntoleranceVerificationStatusCodes (1 uses), AllergyIntoleranceType (1 uses), AllergyIntoleranceCategory (1 uses), AllergyIntoleranceCriticality (1 uses), SubstanceCode (1 uses), SNOMEDCTClinicalFindings (1 uses), AllergyIntoleranceSeverity (1 uses), SNOMEDCTRouteCodes (1 uses), EncounterStatus (2 uses), ServiceType (1 uses), EpisodeOfCare (2 uses), ParticipantType (1 uses), Appointment (1 uses), EncounterReasonCodes (1 uses), DiagnosisRole (1 uses), Account (1 uses), AdmitSource (1 uses), Diet (1 uses), SpecialCourtesy (1 uses), SpecialArrangements (1 uses), EncounterLocationStatus (1 uses), LocationType (2 uses), LocationStatus (1 uses), LocationMode (1 uses), Endpoint (2 uses), MeasureReport (3 uses), MeasureReportStatus (1 uses), MeasureReportType (1 uses), Measure (2 uses), Group (1 uses), MeasureImprovementNotation (1 uses), MeasurePopulationType (2 uses), List (2 uses), OrganizationType (1 uses), ContactEntityType (1 uses), PatientRelationshipType (2 uses), ConditionClinicalStatusCodes (1 uses), ConditionVerificationStatus (1 uses), ConditionCategoryCodes (1 uses), Condition/DiagnosisSeverity (1 uses), ConditionStage (1 uses), ClinicalImpression (1 uses), DiagnosticReport (6 uses), ConditionStageType (1 uses), ManifestationAndSymptomCodes (1 uses), ImmunizationStatusCodes (1 uses), ImmunizationStatusReasonCodes (1 uses), ImmunizationOriginCodes (1 uses), CodesForImmunizationSiteOfAdministration (1 uses), ImmunizationRouteCodes (1 uses), ImmunizationFunctionCodes (1 uses), ImmunizationReasonCodes (1 uses), ImmunizationSubpotentReason (1 uses), ImmunizationProgramEligibility (1 uses), ImmunizationFundingSource (1 uses), ImmunizationTargetDiseaseCodes (1 uses), ObservationCategoryCodes (2 uses), medicationrequest Status (1 uses), medicationRequest Status Reason Codes (1 uses), medicationRequest Intent (1 uses), medicationRequest Category Codes (1 uses), RequestPriority (2 uses), SNOMEDCTMedicationCodes (2 uses), ProcedurePerformerRoleCodes (2 uses), Condition/Problem/DiagnosisCodes (3 uses), medicationRequest Course of Therapy Codes (1 uses), ClaimResponse (2 uses), DetectedIssue (1 uses), Provenance (2 uses), Medication Status Codes (1 uses), SNOMEDCTDrugTherapyStatusCodes (1 uses), Medication usage category codes (1 uses), PlanDefinition (2 uses), ActivityDefinition (2 uses), Questionnaire (1 uses), EventStatus (1 uses), ProcedureCategoryCodes(SNOMEDCT) (1 uses), ProcedureReasonCodes (2 uses), ProcedureOutcomeCodes(SNOMEDCT) (1 uses), Composition (1 uses), ProcedureFollowUpCodes(SNOMEDCT) (1 uses), ProcedureDeviceActionCodes (1 uses), FHIRDeviceTypes (1 uses), RequestStatus (1 uses), RequestIntent (1 uses), ServiceRequestCategoryCodes (1 uses), ServiceRequestOrderDetailsCodes (1 uses), SNOMEDCTMedicationAsNeededReasonCodes (1 uses), ParticipantRoles (1 uses), HealthcareService (1 uses), Shareable ValueSet (1 uses) hl7.fhir.uv.extensions.r4#5.2.0: SDStatusDerivation (53 uses), TypeMustSupport (20 uses)
Modifier Extensions:	(none)
Previous Version Comparison:	Unable to compare with previous version: Unable to find version history at http://hl7.org/fhir/us/dapl (Problem #1 with package-list.json at http://hl7.org/fhir/us/dapl: Not Found)
IPA Comparison:	n/a
IPS Comparison:	n/a
Validation Flags:	On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Narratives Suppressed	AdverseEvent/de-identified-example, AllergyIntolerance/de-identified-example, Observation/de-identified-clinical-result-observation-example, Condition/de-identified-example, Coverage/de-identified-example, Encounter/de-identified-example, Immunization/de-identified-example, Observation/de-identified-lab-observation-example, Location/deidentified-location-example, MedicationRequest/de-identified-example, MedicationStatement/de-identified-example, Observation/de-identified-income-with-quantity-example, Observation/de-identified-income-example, Observation/de-identified-low-income-example, Organization/deidentified-organization-example, Patient/de-identified-age89-example, Patient/de-identified-smallpop-example, Patient/de-identified-example, Procedure/de-identified-example, Procedure/de-identified-not-done-example, RelatedPerson/de-identified-example, ServiceRequest/de-identified-example, MeasureReport/dapl-anonymized-dataset-example, Bundle/dapl-deidentified-bundle
Summary:	errors = 0, warn = 0, info = 0, broken links = 0, pinned = 3 (when multiples). Show Message Ids

n/a Show Validation Information

Suppressed Messages (Warnings, hints, broken links)

Best Practice Recommendation which is not required for DAPL

• Best Practice Recommendation: In general, all observations should have a performer (3 uses)

Dummy Measure as it will be removed in the future.

• The Measure 'http://example.org/Measure/anonymize-data' could not be resolved, so no validation can be performed against the Measure (1 uses)

FHIR US Core Variance Request - https://jira.hl7.org/browse/FHIR-56370

• US FHIR Usage rules require that all profiles on AllergyIntolerance derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (1 uses)
• US FHIR Usage rules require that all profiles on Condition derive from one of the base US profiles. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (1 uses)
• US FHIR Usage rules require that all profiles on Coverage derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (1 uses)
• US FHIR Usage rules require that all profiles on Encounter derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (1 uses)
• US FHIR Usage rules require that all profiles on Immunization derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (1 uses)
• US FHIR Usage rules require that all profiles on Location derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (1 uses)
• US FHIR Usage rules require that all profiles on MedicationRequest derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (1 uses)
• US FHIR Usage rules require that all profiles on Observation derive from one of the base US profiles. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (3 uses)
• US FHIR Usage rules require that all profiles on Observation derive from one of the base US profiles. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (0 uses)
• US FHIR Usage rules require that all profiles on Observation derive from one of the base US profiles. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (0 uses)
• US FHIR Usage rules require that all profiles on Organization derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (1 uses)
• US FHIR Usage rules require that all profiles on Patient derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (1 uses)
• US FHIR Usage rules require that all profiles on Procedure derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (1 uses)
• US FHIR Usage rules require that all profiles on RelatedPerson derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (1 uses)
• US FHIR Usage rules require that all profiles on ServiceRequest derive from one of the base US profiles. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process (1 uses)

Messages due to Base Specification

• The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.2.0 is deprecated (1 uses)
• The extension http://hl7.org/fhir/StructureDefinition/regex|5.2.0 is deprecated with the note: 'This was deprecated in favor of using a constraint on the element using FHIRPath, since constraints allow for the provision of a human readable message associated with the regex' (1 uses)

Pinning of value sets due to the base specification

• Pinned the version of http://terminology.hl7.org/CodeSystem/v3-AdministrativeGender to 4.0.0 from choices of 3.0.0 (hl7.terminology#5.5.0), 4.0.0 (hl7.terminology.r4#7.1.0) (1 uses)
• Pinned the version of http://terminology.hl7.org/ValueSet/v2-0092 to 3.0.0 from choices of 2.0.0 (hl7.terminology#5.5.0), 3.0.0 (hl7.terminology.r4#7.1.0) (1 uses)
• Pinned the version of http://terminology.hl7.org/ValueSet/v2-0116 to 3.0.0 from choices of 2.0.0 (hl7.terminology#5.5.0), 3.0.0 (hl7.terminology.r4#7.1.0) (1 uses)

Resources in DAPL are de-identified and text is not allowed, hence the resources should not have text.

• Constraint failed: dom-6: 'A resource should have narrative for robust management (text.`div`.exists())' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (43 uses)

Errors sorted by type