Loading...

XML

Word

Printable

JSON

Specification:

US Making EHR Data More available for Research and Public Health (MedMorph) (FHIR)
Raised in Version:

0.1.0
Work Group:

Public Health
Related URL:
http://hl7.org/fhir/us/medmorph/2021JAN/StructureDefinition-us-ph-plandefinition.html
Related Artifact(s):

US Public Health PlanDefinition
Grouping:
- Block-Vote-3
Resolution Description:

Hide

All 3 comments will be implemented per the comment by constraining the profiles to the specific values for MedMorph.

Show
All 3 comments will be implemented per the comment by constraining the profiles to the specific values for MedMorph.
Resolution Vote:
Kishore Bashyam / Craig Newman : 28 - 0 - 1
Change Category:
Correction
Change Impact:
Compatible, substantive

Section 6.1.3 (page http://hl7.org/fhir/us/medmorph/2021JAN/provisioning.html) says "MedMorph Knowledge Artifacts SHALL be of type eca-rule or workflow-definition and is represented in PlanDefinition.type attribute." but PlanDefinition.type is not constrained to just those two values. Should it be?
Section 6.1.3 (page http://hl7.org/fhir/us/medmorph/2021JAN/provisioning.html) says "MedMorph Conditions SHALL always be of kind “applicability” and are specified in PlanDefinition.Condition.kind element." but condition.kind is not fixed to this value. Should it be?
Section 6.1.3 (page http://hl7.org/fhir/us/medmorph/2021JAN/provisioning.html) says "The PlanDefinition.action.relatedAction.relationship to be used for MedMorph related actions SHALL be before-start" but the element is not constrained to this value. Should it be?

is voted on by

BALLOT-15023 Affirmative - Craig Newman : 2021-Jan-FHIR IG MEDMORPH R1 STU