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')
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
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)
hl7.fhir.us.dapl
hl7.fhir.uv.extensions
