Observation: cannot redefine the "medicationXChanged" extensions about ch-emed-epr HOT 6 CLOSED

Oh, that's a good hint. I'll have to change the constraint so that it doesn't check the URL, but whether an entry is present and 'conformsTo' the profiles of the extension.

from ch-emed-epr.

@qligier
could you please check, if it works for you with the updated constraint:
http://build.fhir.org/ig/hl7ch/ch-emed/branches/204_obs-constraint/StructureDefinition-ch-emed-observation.html#constraints

from ch-emed-epr.

Thank you!
Now I can override the extensions, but would we be still compatible? Having different extension URLs means more work for implementers, who will have to check for the resources instead of the URL.

Another way to solve this issue could be:

1. I keep the CH-EMED extensions. In the column Type, the CH-EMED types are shown, I update the short to specifically say that the CH-EMED-EPR resources are expected.
2. I add another constraint (or two), checking that the extensions refer to the CH-EMED-EPR resources.

What do you think?

from ch-emed-epr.

You are right with the compatibility...
In that case, do you agree with no changes in CH EMED and updates on your side?

from ch-emed-epr.

It seems to be the best solution to ensure compatibility (as far as I know), so yes, I'll update the resources on my side.

from ch-emed-epr.

Already solved with two additional constraints.

from ch-emed-epr.