Conformance Rule: This will reference the bundle

Target references are usually version specific, but might not be, if a version has not been assigned or if the provenance information is part of the set of resources being maintained (i.e. a document). When using the RESTful API, the identity of the resource might not be known (especially not the version specific one); the client may either submit the resource first, and then the provenance, or it may submit both using a single transaction. See the notes on transaction for further discussion.

***This will likely be a fixed value of "EXPORT"

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.

Conformance Rule: There will be two agents specified in WHO. The first is a reference to exporting device, where the EMR application instance identifier must be specified (PSS1234, MA6777, etc). Example: urn:telus:emr:pss:1234. The name of the EMR software (PSSuite, MedAccess, etc) will also be specified in device. The second agent is a reference to the practitioner who carried out the action; this must be included if known

Conformance Rule: The name of the organization (eg Clinic ABC) will be conveyed in the onBehalfOf.display when the agent.who is the device.

Conformance Rule: The onBehalfOf may be present when the agent.who is the User (clinical or non-clinical) who is acting on behalf of another Practitioner (note: FHIR uses either Practitioner or Practitioner Role resource). Example: A student who is acting in a clinical role will be acting on behalf of a responsible practitioner. Example 2: An MOA will be acting on behalf of the responsible physician.

Several agents may be associated (i.e. has some responsibility for an activity) with an activity and vice-versa.

Conformance Rule: A reference to device must be specified and a reference to either Practitioner (Profile choice of Practitioner or MOA/User) must be specified

whoIdentity should be used when the agent is not a Resource type.

Conformance Rule: This is specified when the agent/user is acting on behalf of Practitioner

Conformance Rule: The PractitonerRole must always be used as this is the means for specifying the role and specialty of the practitioner. If the practitioner role is not known, the Practitioner resource may be used.

onBehalfOfIdentity should be used when the agent is not a Resource type.