Primary Care
0.1.0-dft-preBallot 
dft-preBallot - This is the first draft of the P-Care IG. For a full list of available versions, see the Directory of published versions
Copied Participants
Links
Extension
Description
Identifies a participant who receives a copy of a service request.
References to this Extension
Resource Content
| PCareCopiedParticipants (Extension) | C | Extension | |
| id | 0..1 | string | |
| extension | C | 0..0 | Extension |
| url | 1..1 | uriFixed Value | |
| value[x] | 0..1 | Reference(PCareHealthcareService | PCarePractitioner | PCarePractitionerRole) | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| reference | O Σ C | 0..1 | string |
| type | Σ | 0..1 | uriBinding |
| identifier | O Σ | 0..1 | Identifier |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| use | Σ ?! | 0..1 | codeBinding |
| type | Σ | 0..1 | CodeableConceptBinding |
| system | O Σ | 1..1 | uri |
| value | O Σ | 1..1 | string |
| period | Σ C | 0..1 | Period |
| assigner | Σ C | 0..1 | Reference(Organization) |
| display | Σ | 0..1 | string |
| PCareCopiedParticipants (Extension) | C | Extension | |
| id | 0..1 | string | |
| extension | C | 0..0 | Extension |
| url | 1..1 | uriFixed Value | |
| value[x] | 0..1 | Reference(PCareHealthcareService | PCarePractitioner | PCarePractitionerRole) | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| reference | O Σ C | 0..1 | string |
| type | Σ | 0..1 | uriBinding |
| identifier | O Σ | 0..1 | Identifier |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| use | Σ ?! | 0..1 | codeBinding |
| type | Σ | 0..1 | CodeableConceptBinding |
| system | O Σ | 1..1 | uri |
| value | O Σ | 1..1 | string |
| period | Σ | 0..1 | Period |
| assigner | Σ | 0..1 | Reference(Organization) |
| display | Σ | 0..1 | string |
--- We have skipped the narrative for better readability of the resource ---
</text>
<url value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/pcare-copied-participants" />
</mapping>
</context>
</extension>
</base>
</constraint>
</constraint>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
</base>
</type>
</constraint>
</constraint>
</element>
<comment value="The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension." />
</base>
</extension>
</type>
<fixedUri value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/pcare-copied-participants" />
</mapping>
</element>
<definition value="Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list)." />
</base>
<targetProfile value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner-role" />
<targetProfile value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/healthcare-service" />
</type>
</constraint>
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/pcare-copied-participants|0.1.0" />
</extension>
</extension>
<definition value="A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources." />
<comment value="Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server." />
</base>
</type>
</constraint>
</mapping>
</element>
<definition value="The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.\n\nThe type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources)." />
<comment value="This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified." />
</base>
</type>
</constraint>
</extension>
</binding>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/pcare-copied-participants|0.1.0" />
</extension>
</extension>
<definition value="An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference." />
<comment value="When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. \n\nWhen both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference\n\nApplications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.\n\nReference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any)." />
</base>
</type>
</constraint>
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
<comment value="Applications can assume that an identifier is permanent unless it explicitly says that it is temporary." />
<requirements value="Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers." />
</base>
</type>
</constraint>
<isModifierReason value="This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one." />
</extension>
</binding>
</mapping>
</mapping>
</element>
<definition value="A coded type for the identifier that can be used to determine which identifier to use for a specific purpose." />
<comment value="This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type." />
<requirements value="Allows users to make use of identifiers when the identifier system is not known." />
</base>
</type>
</constraint>
</extension>
<description value="A coded type for an identifier that can be used to determine which identifier to use for a specific purpose." />
</binding>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/pcare-copied-participants|0.1.0" />
</extension>
</extension>
<definition value="Establishes the namespace for the value - that is, a URL that describes a set values that are unique." />
<requirements value="There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers." />
</base>
</type>
</example>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
<valueCanonical value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/pcare-copied-participants|0.1.0" />
</extension>
</extension>
<definition value="The portion of the identifier typically relevant to the user and which is unique within the context of the system." />
<comment value="If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe." />
</base>
</type>
</example>
</constraint>
</mapping>
<map value="II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)" />
</mapping>
</mapping>
</element>
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<comment value="The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization." />
</base>
</type>
</constraint>
</mapping>
<map value="II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper" />
</mapping>
</mapping>
</element>
</extension>
<definition value="Plain text narrative that identifies the resource in addition to the resource reference." />
<comment value="This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it." />
</base>
</type>
</constraint>
</mapping>
</element>
</snapshot>
</element>
</element>
<fixedUri value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/pcare-copied-participants" />
</element>
<targetProfile value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner-role" />
<targetProfile value="http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/healthcare-service" />
</type>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</element>
</differential>
</StructureDefinition>
{
--- We have skipped the narrative for better readability of the resource ---
},
],
],
{
}
],
{
},
"ele-1"
],
{
},
{
}
],
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
},
],
{
},
{
}
],
},
{
"xmlAttr"
],
"comment": "The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.",
},
{
{
}
],
}
],
"fixedUri": "http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/pcare-copied-participants",
]
},
{
"definition": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).",
},
{
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner-role",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/healthcare-service"
]
}
],
{
}
],
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
{
},
{
}
],
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
"valueCanonical": "http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/pcare-copied-participants|0.1.0"
}
],
}
],
"definition": "A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.",
"comment": "Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure \"/[type]/[id]\" then it should be assumed that the reference is to a FHIR RESTful server.",
},
],
"ref-1"
],
{
}
],
]
},
{
"definition": "The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent.\n\nThe type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. \"Patient\" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).",
"comment": "This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.",
},
],
{
}
],
{
}
],
},
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
"valueCanonical": "http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/pcare-copied-participants|0.1.0"
}
],
}
],
"definition": "An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.",
"comment": "When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. \n\nWhen both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference\n\nApplications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.\n\nReference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).",
},
],
{
}
],
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
{
},
{
}
],
]
},
{
"comment": "Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.",
"requirements": "Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.",
},
],
{
}
],
"isModifierReason": "This is labeled as \"Is Modifier\" because applications should not mistake a temporary id for a permanent one.",
{
}
],
},
]
},
{
"definition": "A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.",
"comment": "This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.",
},
],
{
}
],
{
}
],
"description": "A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.",
},
{
},
{
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
"valueCanonical": "http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/pcare-copied-participants|0.1.0"
}
],
}
],
"definition": "Establishes the namespace for the value - that is, a URL that describes a set values that are unique.",
"requirements": "There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.",
},
],
],
{
}
],
{
},
{
},
{
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
"valueCanonical": "http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/pcare-copied-participants|0.1.0"
}
],
}
],
"definition": "The portion of the identifier typically relevant to the user and which is unique within the context of the system.",
"comment": "If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.",
},
],
],
{
}
],
{
},
{
},
{
}
]
},
{
},
],
{
}
],
{
},
{
},
{
}
]
},
{
"comment": "The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.",
},
{
"http://hl7.org/fhir/StructureDefinition/Organization|4.0.1"
]
}
],
{
}
],
{
},
{
"map": "II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper"
},
{
}
]
},
{
{
}
],
"definition": "Plain text narrative that identifies the resource in addition to the resource reference.",
"comment": "This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.",
},
],
{
}
],
]
}
]
},
{
},
{
},
{
},
{
{
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/practitioner-role",
"http://fhir.infoway-inforoute.ca/p-care/StructureDefinition/healthcare-service"
]
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
}
]
}
}