Stream: IG creation
Topic: Communication recipient in DSTU3
Ole Hedegaard (Jun 27 2019 at 08:48):
Hi,
In R4 it is possible to set a CareTeam as a Communication.recipient, but I also need that option in a DSTU3 Communication profile. In Forge it is actually possible to add the CareTeam type as a recipient option, but once I try to set a CareTeam as a recipient on HAPI FHIR (release 3.8) on a new Communication instance, I get this error:
Failure during REST processing: ca.uhn.fhir.rest.server.exceptions.UnprocessableEntityException: Invalid reference found at path 'Communication.recipient'. Resource type 'CareTeam' is not valid for this path
So it seems that HAPI FHIR doesn't support what Forge lets me profile.
Any advise on how to allow Communication.recipient to include a CareTeam?
Vadim Peretokin (Jun 27 2019 at 08:51):
That's correct - you can't extend the standard resource just by picking a reference target that's outside the intended range of targets. At most, you can limit them.
Vadim Peretokin (Jun 27 2019 at 08:52):
You might be able to use the R4 element as an extension in STU3 following these rules: http://hl7.org/fhir/versions.html#extensions
Jens Villadsen (Jun 27 2019 at 09:13):
@Vadim Peretokin @Michel Rutten sounds like a feature request to me on forge, not to let it allow such engineering beyond the scope of the spec
Eric Haas (Jun 27 2019 at 16:32):
you will need an extension to add more types
Sean McIlvenna (Jun 27 2019 at 18:04):
@Eric Haas look here: https://build.fhir.org/ig/HL7/cda-core-2.0/StructureDefinition-ClinicalDocument.html
Go to the differential tab
And look at any of the links in the "Type" column
For example, look at "dataEnterer". The link for the "Type" of the dataEnterer element is https://build.fhir.org/ig/HL7/cda-core-2.0/StructureDefinition/DataEnterer.html when instead it should be https://build.fhir.org/ig/HL7/cda-core-2.0/StructureDefinition-DataEnterer.html
Eric Haas (Jun 27 2019 at 19:01):
oh I see...when that happens to me is a user error.
Last updated: Apr 12 2022 at 19:14 UTC
