This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions 
Detailed Cross Analysis for the definition.
| Definition.url |
| Definition.url : uri [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.url : uri [0..1]
url does not contain the recommended logical text for short (Pattern: Canonical identifier for this activity definition, represented as an absolute URI (globally unique); ; Resource: Canonical identifier for this activity definition, represented as a URI (globally unique)) - no reason provided
url does not contain the recommended logical text for comments (Pattern: Can be a `urn:uuid:` or a `urn:oid:` but real `http/s:` addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.; ; Resource: Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.) - no reason provided
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.url : uri [0..1]
url does not contain the recommended logical text for short (Pattern: Canonical identifier for this charge item definition, represented as an absolute URI (globally unique); ; Resource: Canonical identifier for this charge item definition, represented as a URI (globally unique)) - no reason provided
url does not contain the recommended logical text for comments (Pattern: Can be a `urn:uuid:` or a `urn:oid:` but real `http/s:` addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.; ; Resource: Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.) - no reason provided
|
|
|
|
| EventDefinition |
- EventDefinition.url : uri [0..1]
url does not contain the recommended logical text for short (Pattern: Canonical identifier for this event definition, represented as an absolute URI (globally unique); ; Resource: Canonical identifier for this event definition, represented as a URI (globally unique)) - no reason provided
url does not contain the recommended logical text for comments (Pattern: Can be a `urn:uuid:` or a `urn:oid:` but real `http/s:` addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.; ; Resource: Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.) - no reason provided
|
|
|
|
| Measure |
- Measure.url : uri [0..1]
url does not contain the recommended logical text for short (Pattern: Canonical identifier for this measure, represented as an absolute URI (globally unique); ; Resource: Canonical identifier for this measure, represented as a URI (globally unique)) - no reason provided
url does not contain the recommended logical text for comments (Pattern: Can be a `urn:uuid:` or a `urn:oid:` but real `http/s:` addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.; ; Resource: Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.) - no reason provided
|
|
|
|
| MessageDefinition |
- MessageDefinition.url : uri [0..1]
url does not contain the recommended logical text for short (Pattern: Canonical identifier for this message definition, represented as an absolute URI (globally unique); ; Resource: The cannonical URL for a given MessageDefinition) - no reason provided
url does not contain the recommended logical text for definition (Pattern: An absolute URI that is used to identify this message definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which an authoritative instance of this message definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the message definition is stored on different servers.; ; Resource: The business identifier that is used to reference the MessageDefinition and *is* expected to be consistent from server to server.) - no reason provided
url does not contain the recommended logical text for comments (Pattern: Can be a `urn:uuid:` or a `urn:oid:` but real `http/s:` addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.; ; Resource: Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.) - no reason provided
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.url : uri [0..1]
url does not contain the recommended logical text for short (Pattern: Canonical identifier for this observation definition, represented as an absolute URI (globally unique); ; Resource: Logical canonical URL to reference this ObservationDefinition (globally unique)) - no reason provided
url does not contain the recommended logical text for definition (Pattern: An absolute URI that is used to identify this observation definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which an authoritative instance of this observation definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the observation definition is stored on different servers.; ; Resource: An absolute URL that is used to identify this ObservationDefinition when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this ObservationDefinition is (or will be) published. The URL SHOULD include the major version of the ObservationDefinition. For more information see Technical and Business Versions.) - no reason provided
url does not contain the recommended logical text for comments (Pattern: Can be a `urn:uuid:` or a `urn:oid:` but real `http/s:` addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.; ; Resource: Can be a urn:uuid: or a urn:oid:, but real http: addresses are preferred. This is the URI that will be used when making canonical references to this resource.) - no reason provided
url does not contain the recommended logical text for requirements (Pattern: Allows the observation definition to be referenced by a single globally unique identifier.; ; Resource: Allows the ObservationDefinition to be referenced by a single globally unique identifier.) - no reason provided
|
|
|
|
| OperationDefinition |
- OperationDefinition.url : uri [0..1]
url does not contain the recommended logical text for comments (Pattern: Can be a `urn:uuid:` or a `urn:oid:` but real `http/s:` addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.; ; Resource: Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.) - no reason provided
|
|
|
|
| PlanDefinition |
- PlanDefinition.url : uri [0..1]
url does not contain the recommended logical text for short (Pattern: Canonical identifier for this plan definition, represented as an absolute URI (globally unique); ; Resource: Canonical identifier for this plan definition, represented as a URI (globally unique)) - no reason provided
url does not contain the recommended logical text for comments (Pattern: Can be a `urn:uuid:` or a `urn:oid:` but real `http/s:` addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.; ; Resource: Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.) - no reason provided
|
|
|
|
| Questionnaire |
- Questionnaire.url : uri [0..1]
url does not contain the recommended logical text for comments (Pattern: Can be a `urn:uuid:` or a `urn:oid:` but real `http/s:` addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.; ; Resource: Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.
The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.) - no reason provided
|
|
|
|
| Requirements |
- Requirements.url : uri [0..1]
url does not contain the recommended logical text for short (Pattern: Canonical identifier for this requirements, represented as an absolute URI (globally unique); ; Resource: Canonical identifier for this Requirements, represented as a URI (globally unique)) - no reason provided
url does not contain the recommended logical text for definition (Pattern: An absolute URI that is used to identify this requirements when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which an authoritative instance of this requirements is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the requirements is stored on different servers.; ; Resource: An absolute URI that is used to identify this Requirements when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which an authoritative instance of this Requirements is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the Requirements is stored on different servers.) - no reason provided
url does not contain the recommended logical text for comments (Pattern: Can be a `urn:uuid:` or a `urn:oid:` but real `http/s:` addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.; ; Resource: Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.) - no reason provided
url does not contain the recommended logical text for requirements (Pattern: Allows the requirements to be referenced by a single globally unique identifier.; ; Resource: Allows the Requirements to be referenced by a single globally unique identifier.) - no reason provided
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.url : uri [1..1]
Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided
|
Cardinality Problem. |
|
|
| TestPlan |
- TestPlan.url : uri [0..1]
url does not contain the recommended logical text for short (Pattern: Canonical identifier for this test plan, represented as an absolute URI (globally unique); ; Resource: Canonical identifier for this test plan, represented as a URI (globally unique)) - no reason provided
url does not contain the recommended logical text for comments (Pattern: Can be a `urn:uuid:` or a `urn:oid:` but real `http/s:` addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.; ; Resource: Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.) - no reason provided
|
|
|
|
| TestScript |
- TestScript.url : uri [0..1]
url does not contain the recommended logical text for short (Pattern: Canonical identifier for this test script, represented as an absolute URI (globally unique); ; Resource: Canonical identifier for this test script, represented as a URI (globally unique)) - no reason provided
url does not contain the recommended logical text for comments (Pattern: Can be a `urn:uuid:` or a `urn:oid:` but real `http/s:` addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.; ; Resource: Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](resource.html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](resource.html#meta) element to indicate where the current master source of the resource can be found.) - no reason provided
|
|
|
|
| Definition.identifier |
| Definition.identifier : Identifier [0..*] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.identifier : Identifier [0..*]
identifier does not contain the recommended logical text for short (Pattern: Business identifier for activity definition; ; Resource: Additional identifier for the activity definition) - no reason provided
identifier does not contain the recommended logical text for requirements (Pattern: Allows externally provided and/or usable business identifiers to be easily associated with the activity definition.; ; Resource: Allows externally provided and/or usable business identifiers to be easily associated with the module.) - no reason provided
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.identifier : Identifier [0..*]
identifier does not contain the recommended logical text for short (Pattern: Business identifier for charge item definition; ; Resource: Additional identifier for the charge item definition) - no reason provided
identifier does not contain the recommended logical text for requirements (Pattern: Allows externally provided and/or usable business identifiers to be easily associated with the charge item definition.; ; Resource: Allows externally provided and/or usable business identifiers to be easily associated with the module.) - no reason provided
|
|
|
|
| ClinicalUseDefinition |
- ClinicalUseDefinition.identifier : Identifier [0..*]
identifier does not contain the recommended logical text for short (Pattern: Business identifier for clinical use definition; ; Resource: Business identifier for this issue) - no reason provided
identifier does not contain the recommended logical text for definition (Pattern: A formal identifier that is used to identify this clinical use definition when it is represented in other formats, or referenced in a specification, model, design or an instance.; ; Resource: Business identifier for this issue.) - no reason provided
identifier does not contain the recommended logical text for comments (Pattern: Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this clinical use definition outside of FHIR, where it is not possible to use the logical URI.; ; Resource: ) - no reason provided
identifier does not contain the recommended logical text for requirements (Pattern: Allows externally provided and/or usable business identifiers to be easily associated with the clinical use definition.; ; Resource: ) - no reason provided
|
|
|
|
| EventDefinition |
- EventDefinition.identifier : Identifier [0..*]
identifier does not contain the recommended logical text for short (Pattern: Business identifier for event definition; ; Resource: Additional identifier for the event definition) - no reason provided
identifier does not contain the recommended logical text for requirements (Pattern: Allows externally provided and/or usable business identifiers to be easily associated with the event definition.; ; Resource: Allows externally provided and/or usable business identifiers to be easily associated with the module.) - no reason provided
|
|
|
|
| Measure |
- Measure.identifier : Identifier [0..*]
identifier does not contain the recommended logical text for short (Pattern: Business identifier for measure; ; Resource: Additional identifier for the measure) - no reason provided
identifier does not contain the recommended logical text for requirements (Pattern: Allows externally provided and/or usable business identifiers to be easily associated with the measure.; ; Resource: Allows externally provided and/or usable business identifiers to be easily associated with the module.) - no reason provided
|
|
|
|
| MessageDefinition |
- MessageDefinition.identifier : Identifier [0..*]
identifier does not contain the recommended logical text for short (Pattern: Business identifier for message definition; ; Resource: Business Identifier for a given MessageDefinition) - no reason provided
identifier does not contain the recommended logical text for requirements (Pattern: Allows externally provided and/or usable business identifiers to be easily associated with the message definition.; ; Resource: Allows externally provided and/or usable business identifiers to be easily associated with the module.) - no reason provided
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.identifier : Identifier [0..1]
Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided
identifier does not contain the recommended logical text for short (Pattern: Business identifier for observation definition; ; Resource: Business identifier of the ObservationDefinition) - no reason provided
identifier does not contain the recommended logical text for definition (Pattern: A formal identifier that is used to identify this observation definition when it is represented in other formats, or referenced in a specification, model, design or an instance.; ; Resource: Business identifiers assigned to this ObservationDefinition. by the performer and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.) - no reason provided
identifier does not contain the recommended logical text for comments (Pattern: Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this observation definition outside of FHIR, where it is not possible to use the logical URI.; ; Resource: This is a business identifier, not a resource identifier. It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types.) - no reason provided
identifier does not contain the recommended logical text for requirements (Pattern: Allows externally provided and/or usable business identifiers to be easily associated with the observation definition.; ; Resource: Allows identification of the ObservationDefinition as it is known by various participating systems and in a way that remains consistent across servers.) - no reason provided
|
Cardinality Problem. |
|
|
| PlanDefinition |
- PlanDefinition.identifier : Identifier [0..*]
identifier does not contain the recommended logical text for short (Pattern: Business identifier for plan definition; ; Resource: Additional identifier for the plan definition) - no reason provided
identifier does not contain the recommended logical text for requirements (Pattern: Allows externally provided and/or usable business identifiers to be easily associated with the plan definition.; ; Resource: Allows externally provided and/or usable business identifiers to be easily associated with the module.) - no reason provided
|
|
|
|
| Questionnaire |
- Questionnaire.identifier : Identifier [0..*]
|
|
|
|
| Requirements |
- Requirements.identifier : Identifier [0..*]
identifier does not contain the recommended logical text for short (Pattern: Business identifier for requirements; ; Resource: Additional identifier for the Requirements (business identifier)) - no reason provided
identifier does not contain the recommended logical text for definition (Pattern: A formal identifier that is used to identify this requirements when it is represented in other formats, or referenced in a specification, model, design or an instance.; ; Resource: A formal identifier that is used to identify this Requirements when it is represented in other formats, or referenced in a specification, model, design or an instance.) - no reason provided
identifier does not contain the recommended logical text for comments (Pattern: Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this requirements outside of FHIR, where it is not possible to use the logical URI.; ; Resource: ) - no reason provided
identifier does not contain the recommended logical text for requirements (Pattern: Allows externally provided and/or usable business identifiers to be easily associated with the requirements.; ; Resource: Allows externally provided and/or usable business identifiers to be easily associated with the module.) - no reason provided
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.identifier : Identifier [0..*]
identifier does not contain the recommended logical text for definition (Pattern: A formal identifier that is used to identify this subscription topic when it is represented in other formats, or referenced in a specification, model, design or an instance.; ; Resource: Business identifiers assigned to this subscription topic by the performer and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server.) - no reason provided
identifier does not contain the recommended logical text for comments (Pattern: Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this subscription topic outside of FHIR, where it is not possible to use the logical URI.; ; Resource: Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.) - no reason provided
identifier does not contain the recommended logical text for requirements (Pattern: Allows externally provided and/or usable business identifiers to be easily associated with the subscription topic.; ; Resource: Allows identification of the subscription topic as it is known by various participating systems and in a way that remains consistent across servers.) - no reason provided
|
|
|
|
| TestPlan |
- TestPlan.identifier : Identifier [0..*]
identifier does not contain the recommended logical text for short (Pattern: Business identifier for test plan; ; Resource: Business identifier identifier for the test plan) - no reason provided
identifier does not contain the recommended logical text for requirements (Pattern: Allows externally provided and/or usable business identifiers to be easily associated with the test plan.; ; Resource: Allows externally provided and/or usable business identifiers to be easily associated with the module.) - no reason provided
|
|
|
|
| TestScript |
- TestScript.identifier : Identifier [0..*]
identifier does not contain the recommended logical text for short (Pattern: Business identifier for test script; ; Resource: Additional identifier for the test script) - no reason provided
identifier does not contain the recommended logical text for requirements (Pattern: Allows externally provided and/or usable business identifiers to be easily associated with the test script.; ; Resource: Allows externally provided and/or usable business identifiers to be easily associated with the module.) - no reason provided
|
|
|
|
| Definition.version |
| Definition.version : string [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.version : string [0..1]
version does not contain the recommended logical text for comments (Pattern: There may be different activity definitions that have the same url but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the activity definition with the format. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).; ; Resource: There may be different activity definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the activity definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).) - no reason provided
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.version : string [0..1]
version does not contain the recommended logical text for comments (Pattern: There may be different charge item definitions that have the same url but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the charge item definition with the format. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).; ; Resource: There may be different charge item definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the charge item definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).) - no reason provided
|
|
|
|
| EventDefinition |
- EventDefinition.version : string [0..1]
version does not contain the recommended logical text for comments (Pattern: There may be different event definitions that have the same url but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the event definition with the format. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).; ; Resource: There may be different event definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the event definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).) - no reason provided
|
|
|
|
| Measure |
- Measure.version : string [0..1]
version does not contain the recommended logical text for comments (Pattern: There may be different measures that have the same url but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the measure with the format. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).; ; Resource: There may be different measure instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the measure with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).) - no reason provided
|
|
|
|
| MessageDefinition |
- MessageDefinition.version : string [0..1]
version does not contain the recommended logical text for comments (Pattern: There may be different message definitions that have the same url but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the message definition with the format. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).; ; Resource: There may be different message definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the message definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).) - no reason provided
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.version : string [0..1]
version does not contain the recommended logical text for short (Pattern: Business version of the observation definition; ; Resource: Business version of the ObservationDefinition) - no reason provided
version does not contain the recommended logical text for definition (Pattern: The identifier that is used to identify this version of the observation definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the observation definition author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.; ; Resource: The identifier that is used to identify this version of the ObservationDefinition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the ObservationDefinition author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions are orderable.) - no reason provided
version does not contain the recommended logical text for comments (Pattern: There may be different observation definitions that have the same url but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the observation definition with the format. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).; ; Resource: There may be multiple different instances of an observationDefinition that have the same identifier but different versions.) - no reason provided
|
|
|
|
| OperationDefinition |
- OperationDefinition.version : string [0..1]
|
|
|
|
| PlanDefinition |
- PlanDefinition.version : string [0..1]
version does not contain the recommended logical text for comments (Pattern: There may be different plan definitions that have the same url but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the plan definition with the format. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).; ; Resource: There may be different plan definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the plan definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).) - no reason provided
|
|
|
|
| Questionnaire |
- Questionnaire.version : string [0..1]
|
|
|
|
| Requirements |
- Requirements.version : string [0..1]
version does not contain the recommended logical text for short (Pattern: Business version of the requirements; ; Resource: Business version of the Requirements) - no reason provided
version does not contain the recommended logical text for definition (Pattern: The identifier that is used to identify this version of the requirements when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the requirements author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.; ; Resource: The identifier that is used to identify this version of the Requirements when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the Requirements author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.) - no reason provided
version does not contain the recommended logical text for comments (Pattern: There may be different requirementss that have the same url but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the requirements with the format. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).; ; Resource: There may be different Requirements instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the Requirements with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).) - no reason provided
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.version : string [0..1]
version does not contain the recommended logical text for definition (Pattern: The identifier that is used to identify this version of the subscription topic when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the subscription topic author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.; ; Resource: The identifier that is used to identify this version of the subscription topic when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the Topic author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions are orderable.) - no reason provided
version does not contain the recommended logical text for comments (Pattern: There may be different subscription topics that have the same url but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the subscription topic with the format. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).; ; Resource: There may be multiple different instances of a subscription topic that have the same identifier but different versions.) - no reason provided
|
|
|
|
| TestPlan |
- TestPlan.version : string [0..1]
version does not contain the recommended logical text for definition (Pattern: The identifier that is used to identify this version of the test plan when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the test plan author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.; ; Resource: The identifier that is used to identify this version of the test plan when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the test plan author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.) - no reason provided
version does not contain the recommended logical text for comments (Pattern: There may be different test plans that have the same url but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the test plan with the format. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).; ; Resource: There may be different test plan instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the test plan with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).) - no reason provided
|
|
|
|
| TestScript |
- TestScript.version : string [0..1]
version does not contain the recommended logical text for comments (Pattern: There may be different test scripts that have the same url but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the test script with the format. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).; ; Resource: There may be different test script instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the test script with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](resource.html#bv-format).) - no reason provided
|
|
|
|
| Definition.versionAlgorithm[x] |
| Definition.versionAlgorithm[x] : string|Coding [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.versionAlgorithm[x] : string, Coding [0..1]
|
|
|
|
| EventDefinition |
- EventDefinition.versionAlgorithm[x] : string, Coding [0..1]
|
|
|
|
| Measure |
- Measure.versionAlgorithm[x] : string, Coding [0..1]
|
|
|
|
| OperationDefinition |
- OperationDefinition.versionAlgorithm[x] : string, Coding [0..1]
|
|
|
|
| PlanDefinition |
- PlanDefinition.versionAlgorithm[x] : string, Coding [0..1]
|
|
|
|
| Questionnaire |
- Questionnaire.versionAlgorithm[x] : string, Coding [0..1]
|
|
|
|
| Requirements |
- Requirements.versionAlgorithm[x] : string, Coding [0..1]
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.versionAlgorithm[x] : string, Coding [0..1]
|
|
|
|
| Definition.name |
| Definition.name : string [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.name : string [0..1]
name does not contain the recommended logical text for comments (Pattern: The name is not expected to be globally unique. The name should be a simple alphanumeric type no-whitespace name to ensure that it is machine-processing friendly.; ; Resource: The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.) - no reason provided
name does not contain the recommended logical text for requirements (Pattern: Supports code generation.; ; Resource: Support human navigation and code generation.) - no reason provided
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.name : string [0..1]
name does not contain the recommended logical text for definition (Pattern: A natural language name identifying the charge item definition. This name should be usable as an identifier for the module by machine processing applications such as code generation.; ; Resource: A natural language name identifying the ChargeItemDefinition. This name should be usable as an identifier for the module by machine processing applications such as code generation.) - no reason provided
name does not contain the recommended logical text for comments (Pattern: The name is not expected to be globally unique. The name should be a simple alphanumeric type no-whitespace name to ensure that it is machine-processing friendly.; ; Resource: The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.) - no reason provided
name does not contain the recommended logical text for requirements (Pattern: Supports code generation.; ; Resource: Support human navigation and code generation.) - no reason provided
|
|
|
|
| EventDefinition |
- EventDefinition.name : string [0..1]
name does not contain the recommended logical text for comments (Pattern: The name is not expected to be globally unique. The name should be a simple alphanumeric type no-whitespace name to ensure that it is machine-processing friendly.; ; Resource: The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.) - no reason provided
name does not contain the recommended logical text for requirements (Pattern: Supports code generation.; ; Resource: Support human navigation and code generation.) - no reason provided
|
|
|
|
| Measure |
- Measure.name : string [0..1]
name does not contain the recommended logical text for comments (Pattern: The name is not expected to be globally unique. The name should be a simple alphanumeric type no-whitespace name to ensure that it is machine-processing friendly.; ; Resource: The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.) - no reason provided
name does not contain the recommended logical text for requirements (Pattern: Supports code generation.; ; Resource: Support human navigation and code generation.) - no reason provided
|
|
|
|
| MessageDefinition |
- MessageDefinition.name : string [0..1]
name does not contain the recommended logical text for comments (Pattern: The name is not expected to be globally unique. The name should be a simple alphanumeric type no-whitespace name to ensure that it is machine-processing friendly.; ; Resource: The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.) - no reason provided
name does not contain the recommended logical text for requirements (Pattern: Supports code generation.; ; Resource: Support human navigation and code generation.) - no reason provided
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.name : string [0..1]
name does not contain the recommended logical text for short (Pattern: Name for this observation definition (computer friendly); ; Resource: Name for this ObservationDefinition (computer friendly)) - no reason provided
name does not contain the recommended logical text for definition (Pattern: A natural language name identifying the observation definition. This name should be usable as an identifier for the module by machine processing applications such as code generation.; ; Resource: A natural language name identifying the ObservationDefinition. This name should be usable as an identifier for the module by machine processing applications such as code generation.) - no reason provided
name does not contain the recommended logical text for comments (Pattern: The name is not expected to be globally unique. The name should be a simple alphanumeric type no-whitespace name to ensure that it is machine-processing friendly.; ; Resource: The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.) - no reason provided
name does not contain the recommended logical text for requirements (Pattern: Supports code generation.; ; Resource: Support human navigation and code generation.) - no reason provided
|
|
|
|
| OperationDefinition |
- OperationDefinition.name : string [1..1]
Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided
name does not contain the recommended logical text for requirements (Pattern: Supports code generation.; ; Resource: Support code generation.) - no reason provided
|
Cardinality Problem. |
|
|
| PlanDefinition |
- PlanDefinition.name : string [0..1]
name does not contain the recommended logical text for comments (Pattern: The name is not expected to be globally unique. The name should be a simple alphanumeric type no-whitespace name to ensure that it is machine-processing friendly.; ; Resource: The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.) - no reason provided
name does not contain the recommended logical text for requirements (Pattern: Supports code generation.; ; Resource: Support human navigation and code generation.) - no reason provided
|
|
|
|
| Questionnaire |
- Questionnaire.name : string [0..1]
|
|
|
|
| Requirements |
- Requirements.name : string [0..1]
name does not contain the recommended logical text for short (Pattern: Name for this requirements (computer friendly); ; Resource: Name for this Requirements (computer friendly)) - no reason provided
name does not contain the recommended logical text for definition (Pattern: A natural language name identifying the requirements. This name should be usable as an identifier for the module by machine processing applications such as code generation.; ; Resource: A natural language name identifying the Requirements. This name should be usable as an identifier for the module by machine processing applications such as code generation.) - no reason provided
name does not contain the recommended logical text for comments (Pattern: The name is not expected to be globally unique. The name should be a simple alphanumeric type no-whitespace name to ensure that it is machine-processing friendly.; ; Resource: The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.) - no reason provided
name does not contain the recommended logical text for requirements (Pattern: Supports code generation.; ; Resource: Support human navigation and code generation.) - no reason provided
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.name : string [0..1]
name does not contain the recommended logical text for definition (Pattern: A natural language name identifying the subscription topic. This name should be usable as an identifier for the module by machine processing applications such as code generation.; ; Resource: A natural language name identifying the subscription topic This name should be usable as an identifier for the module by machine processing applications such as code generation.) - no reason provided
name does not contain the recommended logical text for comments (Pattern: The name is not expected to be globally unique. The name should be a simple alphanumeric type no-whitespace name to ensure that it is machine-processing friendly.; ; Resource: The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.) - no reason provided
name does not contain the recommended logical text for requirements (Pattern: Supports code generation.; ; Resource: Support human navigation and code generation.) - no reason provided
|
|
|
|
| TestPlan |
- TestPlan.name : string [0..1]
name does not contain the recommended logical text for comments (Pattern: The name is not expected to be globally unique. The name should be a simple alphanumeric type no-whitespace name to ensure that it is machine-processing friendly.; ; Resource: The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.) - no reason provided
name does not contain the recommended logical text for requirements (Pattern: Supports code generation.; ; Resource: Support code generation.) - no reason provided
|
|
|
|
| TestScript |
- TestScript.name : string [1..1]
Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided
name does not contain the recommended logical text for comments (Pattern: The name is not expected to be globally unique. The name should be a simple alphanumeric type no-whitespace name to ensure that it is machine-processing friendly.; ; Resource: The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.) - no reason provided
name does not contain the recommended logical text for requirements (Pattern: Supports code generation.; ; Resource: Support code generation.) - no reason provided
|
Cardinality Problem. |
|
|
| Definition.title |
| Definition.title : string [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.title : string [0..1]
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.title : string [0..1]
|
|
|
|
| EventDefinition |
- EventDefinition.title : string [0..1]
|
|
|
|
| Measure |
- Measure.title : string [0..1]
|
|
|
|
| MessageDefinition |
- MessageDefinition.title : string [0..1]
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.title : string [0..1]
title does not contain the recommended logical text for short (Pattern: Name for this observation definition (human friendly); ; Resource: Name for this ObservationDefinition (human friendly)) - no reason provided
title does not contain the recommended logical text for definition (Pattern: A short, descriptive, user-friendly title for the observation definition.; ; Resource: A short, descriptive, user-friendly title for the ObservationDefinition.) - no reason provided
title does not contain the recommended logical text for comments (Pattern: This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; ; Resource: ) - no reason provided
|
|
|
|
| OperationDefinition |
- OperationDefinition.title : string [0..1]
|
|
|
|
| PlanDefinition |
- PlanDefinition.title : string [0..1]
- PlanDefinition.action.title : string [0..1]
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
title does not contain the recommended logical text for short (Pattern: Name for this plan definition (human friendly); ; Resource: User-visible title) - no reason provided
title does not contain the recommended logical text for definition (Pattern: A short, descriptive, user-friendly title for the plan definition.; ; Resource: The textual description of the action displayed to a user. For example, when the action is a test to be performed, the title would be the title of the test such as Assay by HPLC.) - no reason provided
title does not contain the recommended logical text for comments (Pattern: This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; ; Resource: ) - no reason provided
|
|
|
|
| Questionnaire |
- Questionnaire.title : string [0..1]
|
|
|
|
| Requirements |
- Requirements.title : string [0..1]
title does not contain the recommended logical text for short (Pattern: Name for this requirements (human friendly); ; Resource: Name for this Requirements (human friendly)) - no reason provided
title does not contain the recommended logical text for definition (Pattern: A short, descriptive, user-friendly title for the requirements.; ; Resource: A short, descriptive, user-friendly title for the Requirements.) - no reason provided
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.title : string [0..1]
|
|
|
|
| TestPlan |
- TestPlan.title : string [0..1]
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
|
|
|
|
| TestScript |
- TestScript.title : string [0..1]
|
|
|
|
| Definition.derivedFromCanonical |
| Definition.derivedFromCanonical : canonical(Definition) [0..*] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| OperationDefinition |
- OperationDefinition.base : canonical [0..1]
Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided
Resource does not support types that are part of the pattern (Pattern: canonical(Definition)) - no reason provided
Resource supports types that are not part of the pattern (; Resource: canonical(OperationDefinition)) - no reason provided
derivedFromCanonical does not contain the recommended logical text for short (Pattern: Based on FHIR protocol or definition; ; Resource: Marks this as a profile of the base) - no reason provided
derivedFromCanonical does not contain the recommended logical text for definition (Pattern: The canonical URL pointing to another FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this definition.; ; Resource: Indicates that this operation definition is a constraining profile on the base.) - no reason provided
derivedFromCanonical does not contain the recommended logical text for requirements (Pattern: Protocols and order sets may be refinements of more generic protocols and order sets.; ; Resource: ) - no reason provided
|
Names are different.
Type Mismatch.
Cardinality Problem. |
|
|
| Questionnaire |
- Questionnaire.derivedFrom : canonical [0..*]
Resource does not support types that are part of the pattern (Pattern: canonical(Definition)) - no reason provided
Resource supports types that are not part of the pattern (; Resource: canonical(Questionnaire)) - no reason provided
derivedFromCanonical does not contain the recommended logical text for short (Pattern: Based on FHIR protocol or definition; ; Resource: Based on Questionnaire) - no reason provided
derivedFromCanonical does not contain the recommended logical text for definition (Pattern: The canonical URL pointing to another FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this definition.; ; Resource: The URL of a Questionnaire that this Questionnaire is based on.) - no reason provided
derivedFromCanonical does not contain the recommended logical text for requirements (Pattern: Protocols and order sets may be refinements of more generic protocols and order sets.; ; Resource: Allows a Questionnaire to be created based on another Questionnaire.) - no reason provided
|
Names are different.
Type Mismatch. |
|
|
| Requirements |
- Requirements.derivedFrom : canonical [0..*]
Resource does not support types that are part of the pattern (Pattern: canonical(Definition)) - no reason provided
Resource supports types that are not part of the pattern (; Resource: canonical(Requirements)) - no reason provided
derivedFromCanonical does not contain the recommended logical text for short (Pattern: Based on FHIR protocol or definition; ; Resource: Other set of Requirements this builds on) - no reason provided
derivedFromCanonical does not contain the recommended logical text for definition (Pattern: The canonical URL pointing to another FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this definition.; ; Resource: Another set of Requirements that this set of Requirements builds on and updates.) - no reason provided
derivedFromCanonical does not contain the recommended logical text for requirements (Pattern: Protocols and order sets may be refinements of more generic protocols and order sets.; ; Resource: ) - no reason provided
|
Names are different.
Type Mismatch. |
|
|
| SubscriptionTopic |
- SubscriptionTopic.derivedFrom : canonical [0..*]
Resource does not support types that are part of the pattern (Pattern: canonical(Definition)) - no reason provided
Resource supports types that are not part of the pattern (; Resource: canonical(SubscriptionTopic)) - no reason provided
derivedFromCanonical does not contain the recommended logical text for definition (Pattern: The canonical URL pointing to another FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this definition.; ; Resource: The canonical URL pointing to another FHIR-defined SubscriptionTopic that is adhered to in whole or in part by this SubscriptionTopic.) - no reason provided
derivedFromCanonical does not contain the recommended logical text for requirements (Pattern: Protocols and order sets may be refinements of more generic protocols and order sets.; ; Resource: SubscriptionTopics may be refinements of more generic topics.) - no reason provided
|
Names are different.
Type Mismatch. |
|
|
| Definition.derivedFromUri |
| Definition.derivedFromUri : uri [0..*] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| Definition.partOf |
| Definition.partOf : canonical(Definition) [0..*] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| Definition.status |
| Definition.status : code [1..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.status : code [1..1]
status does not contain the recommended logical text for definition (Pattern: The current state of this activity definition.; ; Resource: The status of this activity definition. Enables tracking the life-cycle of the content.) - no reason provided
status does not contain the recommended logical text for comments (Pattern: A nominal state-transition diagram can be found in the] documentation
Unknown does not represent 'other' - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.; ; Resource: Allows filtering of activity definitions that are appropriate for use versus not.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
status does not contain the recommended logical text for requirements (Pattern: Enables tracking the lifecycle of the content and filtering of activity definitions that are appropriate for use versus not.; ; Resource: ) - no reason provided
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.status : code [1..1]
status does not contain the recommended logical text for definition (Pattern: The current state of this charge item definition.; ; Resource: The current state of the ChargeItemDefinition.) - no reason provided
status does not contain the recommended logical text for comments (Pattern: A nominal state-transition diagram can be found in the] documentation
Unknown does not represent 'other' - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.; ; Resource: Allows filtering of charge item definitions that are appropriate for use versus not.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
status does not contain the recommended logical text for requirements (Pattern: Enables tracking the lifecycle of the content and filtering of charge item definitions that are appropriate for use versus not.; ; Resource: ) - no reason provided
|
|
|
|
| ClinicalUseDefinition |
- ClinicalUseDefinition.status : CodeableConcept [0..1]
Minimum Cardinality differs (Pattern: 1; ; Resource: 0) - no reason provided
Resource does not support types that are part of the pattern (Pattern: code) - no reason provided
Resource supports types that are not part of the pattern (; Resource: CodeableConcept) - no reason provided
IsModifier differs (Pattern: true; ; Resource: false) - no reason provided
Binding strengths differ (Pattern: required; ; Resource: preferred) - no reason provided
status does not contain the recommended logical text for short (Pattern: draft | active | retired | unknown; ; Resource: Whether this is a current issue or one that has been retired etc) - no reason provided
status does not contain the recommended logical text for definition (Pattern: The current state of this clinical use definition.; ; Resource: Whether this is a current issue or one that has been retired etc.) - no reason provided
status does not contain the recommended logical text for comments (Pattern: A nominal state-transition diagram can be found in the] documentation
Unknown does not represent 'other' - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.; ; Resource: ) - no reason provided
status does not contain the recommended logical text for requirements (Pattern: Enables tracking the lifecycle of the content and filtering of clinical use definitions that are appropriate for use versus not.; ; Resource: ) - no reason provided
|
Type Mismatch.
Cardinality Problem. |
|
|
| EventDefinition |
- EventDefinition.status : code [1..1]
status does not contain the recommended logical text for definition (Pattern: The current state of this event definition.; ; Resource: The status of this event definition. Enables tracking the life-cycle of the content.) - no reason provided
status does not contain the recommended logical text for comments (Pattern: A nominal state-transition diagram can be found in the] documentation
Unknown does not represent 'other' - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.; ; Resource: Allows filtering of event definitions that are appropriate for use versus not.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
status does not contain the recommended logical text for requirements (Pattern: Enables tracking the lifecycle of the content and filtering of event definitions that are appropriate for use versus not.; ; Resource: ) - no reason provided
|
|
|
|
| Measure |
- Measure.status : code [1..1]
status does not contain the recommended logical text for definition (Pattern: The current state of this measure.; ; Resource: The status of this measure. Enables tracking the life-cycle of the content.) - no reason provided
status does not contain the recommended logical text for comments (Pattern: A nominal state-transition diagram can be found in the] documentation
Unknown does not represent 'other' - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.; ; Resource: Allows filtering of measures that are appropriate for use versus not.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
status does not contain the recommended logical text for requirements (Pattern: Enables tracking the lifecycle of the content and filtering of measures that are appropriate for use versus not.; ; Resource: ) - no reason provided
|
|
|
|
| MessageDefinition |
- MessageDefinition.status : code [1..1]
status does not contain the recommended logical text for definition (Pattern: The current state of this message definition.; ; Resource: The status of this message definition. Enables tracking the life-cycle of the content.) - no reason provided
status does not contain the recommended logical text for comments (Pattern: A nominal state-transition diagram can be found in the] documentation
Unknown does not represent 'other' - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.; ; Resource: Allows filtering of message definitions that are appropriate for use versus not.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
status does not contain the recommended logical text for requirements (Pattern: Enables tracking the lifecycle of the content and filtering of message definitions that are appropriate for use versus not.; ; Resource: ) - no reason provided
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.status : code [1..1]
status does not contain the recommended logical text for definition (Pattern: The current state of this observation definition.; ; Resource: The current state of the ObservationDefinition.) - no reason provided
status does not contain the recommended logical text for comments (Pattern: A nominal state-transition diagram can be found in the] documentation
Unknown does not represent 'other' - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.; ; Resource: A nominal state-transition diagram can be found in the [Definition pattern](definition.html#statemachine) documentation
Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
status does not contain the recommended logical text for requirements (Pattern: Enables tracking the lifecycle of the content and filtering of observation definitions that are appropriate for use versus not.; ; Resource: ) - no reason provided
|
|
|
|
| OperationDefinition |
- OperationDefinition.status : code [1..1]
|
|
|
|
| PlanDefinition |
- PlanDefinition.status : code [1..1]
status does not contain the recommended logical text for definition (Pattern: The current state of this plan definition.; ; Resource: The status of this plan definition. Enables tracking the life-cycle of the content.) - no reason provided
status does not contain the recommended logical text for comments (Pattern: A nominal state-transition diagram can be found in the] documentation
Unknown does not represent 'other' - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.; ; Resource: Allows filtering of plan definitions that are appropriate for use versus not.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
status does not contain the recommended logical text for requirements (Pattern: Enables tracking the lifecycle of the content and filtering of plan definitions that are appropriate for use versus not.; ; Resource: ) - no reason provided
|
|
|
|
| Questionnaire |
- Questionnaire.status : code [1..1]
|
|
|
|
| Requirements |
- Requirements.status : code [1..1]
status does not contain the recommended logical text for definition (Pattern: The current state of this requirements.; ; Resource: The status of this Requirements. Enables tracking the life-cycle of the content.) - no reason provided
status does not contain the recommended logical text for comments (Pattern: A nominal state-transition diagram can be found in the] documentation
Unknown does not represent 'other' - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.; ; Resource: Allows filtering of Requirements that are appropriate for use versus not.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
status does not contain the recommended logical text for requirements (Pattern: Enables tracking the lifecycle of the content and filtering of requirementss that are appropriate for use versus not.; ; Resource: ) - no reason provided
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.status : code [1..1]
status does not contain the recommended logical text for definition (Pattern: The current state of this subscription topic.; ; Resource: The current state of the SubscriptionTopic.) - no reason provided
status does not contain the recommended logical text for comments (Pattern: A nominal state-transition diagram can be found in the] documentation
Unknown does not represent 'other' - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.; ; Resource: A nominal state-transition diagram can be found in the [Definition pattern](definition.html#statemachine) documentation
Unknown does not represent "other" - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
status does not contain the recommended logical text for requirements (Pattern: Enables tracking the lifecycle of the content and filtering of subscription topics that are appropriate for use versus not.; ; Resource: ) - no reason provided
|
|
|
|
| TestPlan |
- TestPlan.status : code [1..1]
status does not contain the recommended logical text for definition (Pattern: The current state of this test plan.; ; Resource: The status of this test plan. Enables tracking the life-cycle of the content.) - no reason provided
status does not contain the recommended logical text for comments (Pattern: A nominal state-transition diagram can be found in the] documentation
Unknown does not represent 'other' - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.; ; Resource: Allows filtering of test plans that are appropriate for use versus not.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
status does not contain the recommended logical text for requirements (Pattern: Enables tracking the lifecycle of the content and filtering of test plans that are appropriate for use versus not.; ; Resource: ) - no reason provided
|
|
|
|
| TestScript |
- TestScript.status : code [1..1]
status does not contain the recommended logical text for definition (Pattern: The current state of this test script.; ; Resource: The status of this test script. Enables tracking the life-cycle of the content.) - no reason provided
status does not contain the recommended logical text for comments (Pattern: A nominal state-transition diagram can be found in the] documentation
Unknown does not represent 'other' - one of the defined statuses must apply. Unknown is used when the authoring system is not sure what the current status is.; ; Resource: Allows filtering of test scripts that are appropriate for use versus not.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
status does not contain the recommended logical text for requirements (Pattern: Enables tracking the lifecycle of the content and filtering of test scripts that are appropriate for use versus not.; ; Resource: ) - no reason provided
|
|
|
|
| Definition.experimental |
| Definition.experimental : boolean [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.experimental : boolean [0..1]
experimental does not contain the recommended logical text for definition (Pattern: A Boolean value to indicate that this activity definition is authored for testing purposes (or education/evaluation/marketing) and is not intended for genuine usage.; ; Resource: A Boolean value to indicate that this activity definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.) - no reason provided
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.experimental : boolean [0..1]
experimental does not contain the recommended logical text for definition (Pattern: A Boolean value to indicate that this charge item definition is authored for testing purposes (or education/evaluation/marketing) and is not intended for genuine usage.; ; Resource: A Boolean value to indicate that this charge item definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.) - no reason provided
|
|
|
|
| EventDefinition |
- EventDefinition.experimental : boolean [0..1]
experimental does not contain the recommended logical text for definition (Pattern: A Boolean value to indicate that this event definition is authored for testing purposes (or education/evaluation/marketing) and is not intended for genuine usage.; ; Resource: A Boolean value to indicate that this event definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.) - no reason provided
|
|
|
|
| Measure |
- Measure.experimental : boolean [0..1]
experimental does not contain the recommended logical text for definition (Pattern: A Boolean value to indicate that this measure is authored for testing purposes (or education/evaluation/marketing) and is not intended for genuine usage.; ; Resource: A Boolean value to indicate that this measure is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.) - no reason provided
|
|
|
|
| MessageDefinition |
- MessageDefinition.experimental : boolean [0..1]
experimental does not contain the recommended logical text for definition (Pattern: A Boolean value to indicate that this message definition is authored for testing purposes (or education/evaluation/marketing) and is not intended for genuine usage.; ; Resource: A Boolean value to indicate that this message definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.) - no reason provided
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.experimental : boolean [0..1]
experimental does not contain the recommended logical text for short (Pattern: For testing purposes, not real usage; ; Resource: If for testing purposes, not real usage) - no reason provided
experimental does not contain the recommended logical text for definition (Pattern: A Boolean value to indicate that this observation definition is authored for testing purposes (or education/evaluation/marketing) and is not intended for genuine usage.; ; Resource: A flag to indicate that this ObservationDefinition is authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usage.) - no reason provided
experimental does not contain the recommended logical text for comments (Pattern: Allows filtering of observation definitions that are appropriate for use versus not.; ; Resource: Allows filtering of ObservationDefinition that are appropriate for use vs. not.) - no reason provided
experimental does not contain the recommended logical text for requirements (Pattern: Enables experimental content to be developed following the same lifecycle that would be used for a production-level observation definition.; ; Resource: ) - no reason provided
|
|
|
|
| OperationDefinition |
- OperationDefinition.experimental : boolean [0..1]
|
|
|
|
| PlanDefinition |
- PlanDefinition.experimental : boolean [0..1]
experimental does not contain the recommended logical text for definition (Pattern: A Boolean value to indicate that this plan definition is authored for testing purposes (or education/evaluation/marketing) and is not intended for genuine usage.; ; Resource: A Boolean value to indicate that this plan definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.) - no reason provided
|
|
|
|
| Questionnaire |
- Questionnaire.experimental : boolean [0..1]
|
|
|
|
| Requirements |
- Requirements.experimental : boolean [0..1]
experimental does not contain the recommended logical text for definition (Pattern: A Boolean value to indicate that this requirements is authored for testing purposes (or education/evaluation/marketing) and is not intended for genuine usage.; ; Resource: A Boolean value to indicate that this Requirements is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.) - no reason provided
experimental does not contain the recommended logical text for comments (Pattern: Allows filtering of requirementss that are appropriate for use versus not.; ; Resource: Allows filtering of Requirements that are appropriate for use versus not.) - no reason provided
experimental does not contain the recommended logical text for requirements (Pattern: Enables experimental content to be developed following the same lifecycle that would be used for a production-level requirements.; ; Resource: Enables experimental content to be developed following the same lifecycle that would be used for a production-level Requirements.) - no reason provided
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.experimental : boolean [0..1]
experimental does not contain the recommended logical text for short (Pattern: For testing purposes, not real usage; ; Resource: If for testing purposes, not real usage) - no reason provided
experimental does not contain the recommended logical text for definition (Pattern: A Boolean value to indicate that this subscription topic is authored for testing purposes (or education/evaluation/marketing) and is not intended for genuine usage.; ; Resource: A flag to indicate that this TopSubscriptionTopicic is authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usage.) - no reason provided
experimental does not contain the recommended logical text for comments (Pattern: Allows filtering of subscription topics that are appropriate for use versus not.; ; Resource: Allows filtering of SubscriptionTopic that are appropriate for use vs. not.) - no reason provided
experimental does not contain the recommended logical text for requirements (Pattern: Enables experimental content to be developed following the same lifecycle that would be used for a production-level subscription topic.; ; Resource: Enables experimental content to be developed following the same life-cycle as a production-level SubscriptionTopic would.) - no reason provided
|
|
|
|
| TestPlan |
- TestPlan.experimental : boolean [0..1]
experimental does not contain the recommended logical text for definition (Pattern: A Boolean value to indicate that this test plan is authored for testing purposes (or education/evaluation/marketing) and is not intended for genuine usage.; ; Resource: A Boolean value to indicate that this test plan is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.) - no reason provided
|
|
|
|
| TestScript |
- TestScript.experimental : boolean [0..1]
experimental does not contain the recommended logical text for definition (Pattern: A Boolean value to indicate that this test script is authored for testing purposes (or education/evaluation/marketing) and is not intended for genuine usage.; ; Resource: A Boolean value to indicate that this test script is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.) - no reason provided
|
|
|
|
| Definition.subject |
| Definition.subject : CodeableReference(Group) [0..*] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.subject[x] : CodeableConcept, Reference, canonical [0..1]
Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided
Resource does not support types that are part of the pattern (Pattern: CodeableReference(Group)) - no reason provided
Resource supports types that are not part of the pattern (; Resource: Reference(Group,MedicinalProductDefinition,SubstanceDefinition,AdministrableProductDefinition,ManufacturedItemDefinition,PackagedProductDefinition), canonical(EvidenceVariable), CodeableConcept) - no reason provided
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
Binding strengths differ (Pattern: example; ; Resource: extensible) - no reason provided
subject does not contain the recommended logical text for short (Pattern: Type of individual the defined service is for; ; Resource: Type of individual the activity definition is intended for) - no reason provided
subject does not contain the recommended logical text for definition (Pattern: A code or group definition that describes the intended subject of instantiations of this definition.; ; Resource: A code, group definition, or canonical reference that describes or identifies the intended subject of the activity being defined. Canonical references are allowed to support the definition of protocols for drug and substance quality specifications, and is allowed to reference a MedicinalProductDefinition, SubstanceDefinition, AdministrableProductDefinition, ManufacturedItemDefinition, or PackagedProductDefinition resource.) - no reason provided
subject does not contain the recommended logical text for requirements (Pattern: Many protocols, order sets and guidelines are intended for use only with specific types of patients or subjects.; ; Resource: ) - no reason provided
|
Names are different.
Type Mismatch.
Cardinality Problem. |
|
|
| ClinicalUseDefinition |
- ClinicalUseDefinition.subject : Reference [0..*]
Resource does not support types that are part of the pattern (Pattern: CodeableReference(Group)) - no reason provided
Resource supports types that are not part of the pattern (; Resource: Reference(MedicinalProductDefinition,Medication,ActivityDefinition,PlanDefinition,Device,DeviceDefinition,Substance,NutritionProduct,BiologicallyDerivedProduct)) - no reason provided
Only one element has bindings (Pattern: true; ; Resource: false) - no reason provided
subject does not contain the recommended logical text for short (Pattern: Type of individual the defined service is for; ; Resource: The medication, product, substance, device, procedure etc. for which this is an indication, contraindication, interaction, undesirable effect, or warning) - no reason provided
subject does not contain the recommended logical text for definition (Pattern: A code or group definition that describes the intended subject of instantiations of this definition.; ; Resource: The medication, product, substance, device, procedure etc. for which this is an indication, contraindication, interaction, undesirable effect, or warning.) - no reason provided
subject does not contain the recommended logical text for requirements (Pattern: Many protocols, order sets and guidelines are intended for use only with specific types of patients or subjects.; ; Resource: ) - no reason provided
|
Type Mismatch. |
|
|
| EventDefinition |
- EventDefinition.subject[x] : CodeableConcept, Reference [0..1]
Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided
Resource does not support types that are part of the pattern (Pattern: CodeableReference(Group)) - no reason provided
Resource supports types that are not part of the pattern (; Resource: Reference(Group), CodeableConcept) - no reason provided
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
Binding strengths differ (Pattern: example; ; Resource: extensible) - no reason provided
subject does not contain the recommended logical text for short (Pattern: Type of individual the defined service is for; ; Resource: Type of individual the event definition is focused on) - no reason provided
subject does not contain the recommended logical text for definition (Pattern: A code or group definition that describes the intended subject of instantiations of this definition.; ; Resource: A code or group definition that describes the intended subject of the event definition.) - no reason provided
subject does not contain the recommended logical text for requirements (Pattern: Many protocols, order sets and guidelines are intended for use only with specific types of patients or subjects.; ; Resource: ) - no reason provided
|
Names are different.
Type Mismatch.
Cardinality Problem. |
|
|
| PlanDefinition |
- PlanDefinition.subject[x] : CodeableConcept, Reference, canonical [0..1]
Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided
Resource does not support types that are part of the pattern (Pattern: CodeableReference(Group)) - no reason provided
Resource supports types that are not part of the pattern (; Resource: Reference(Group,MedicinalProductDefinition,SubstanceDefinition,AdministrableProductDefinition,ManufacturedItemDefinition,PackagedProductDefinition), canonical(EvidenceVariable), CodeableConcept) - no reason provided
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
Binding strengths differ (Pattern: example; ; Resource: extensible) - no reason provided
subject does not contain the recommended logical text for short (Pattern: Type of individual the defined service is for; ; Resource: Type of individual the plan definition is focused on) - no reason provided
subject does not contain the recommended logical text for definition (Pattern: A code or group definition that describes the intended subject of instantiations of this definition.; ; Resource: A code, group definition, or canonical reference that describes or identifies the intended subject of the plan definition. Canonical references are allowed to support the definition of protocols for drug and substance quality specifications, and is allowed to reference a MedicinalProductDefinition, SubstanceDefinition, AdministrableProductDefinition, ManufacturedItemDefinition, or PackagedProductDefinition resource.) - no reason provided
subject does not contain the recommended logical text for requirements (Pattern: Many protocols, order sets and guidelines are intended for use only with specific types of patients or subjects.; ; Resource: ) - no reason provided- PlanDefinition.topic : CodeableConcept [0..*]
Resource does not support types that are part of the pattern (Pattern: CodeableReference(Group)) - no reason provided
Resource supports types that are not part of the pattern (; Resource: CodeableConcept) - no reason provided
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
subject does not contain the recommended logical text for short (Pattern: Type of individual the defined service is for; ; Resource: E.g. Education, Treatment, Assessment) - no reason provided
subject does not contain the recommended logical text for definition (Pattern: A code or group definition that describes the intended subject of instantiations of this definition.; ; Resource: Descriptive topics related to the content of the plan definition. Topics provide a high-level categorization of the definition that can be useful for filtering and searching.) - no reason provided
subject does not contain the recommended logical text for requirements (Pattern: Many protocols, order sets and guidelines are intended for use only with specific types of patients or subjects.; ; Resource: Repositories must be able to determine how to categorize the plan definition so that it can be found by topical searches.) - no reason provided- PlanDefinition.action.subject[x] : CodeableConcept, Reference, canonical [0..1]
Maximum Cardinality differs (Pattern: *; ; Resource: 1) - no reason provided
Resource does not support types that are part of the pattern (Pattern: CodeableReference(Group)) - no reason provided
Resource supports types that are not part of the pattern (; Resource: Reference(Group), canonical, CodeableConcept) - no reason provided
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
Binding strengths differ (Pattern: example; ; Resource: extensible) - no reason provided
subject does not contain the recommended logical text for short (Pattern: Type of individual the defined service is for; ; Resource: Type of individual the action is focused on) - no reason provided
subject does not contain the recommended logical text for definition (Pattern: A code or group definition that describes the intended subject of instantiations of this definition.; ; Resource: A code, group definition, or canonical reference that describes the intended subject of the action and its children, if any. Canonical references are allowed to support the definition of protocols for drug and substance quality specifications, and is allowed to reference a MedicinalProductDefinition, SubstanceDefinition, AdministrableProductDefinition, ManufacturedItemDefinition, or PackagedProductDefinition resource.) - no reason provided
subject does not contain the recommended logical text for requirements (Pattern: Many protocols, order sets and guidelines are intended for use only with specific types of patients or subjects.; ; Resource: Multiple steps in a protocol often have different groups of steps that are focused on testing different things. The subject of an action specifies the focus of the action and any child actions.) - no reason provided
|
Names are different.
Type Mismatch.
Cardinality Problem. |
|
|
| Questionnaire |
- Questionnaire.subjectType : code [0..*]
Resource does not support types that are part of the pattern (Pattern: CodeableReference(Group)) - no reason provided
Resource supports types that are not part of the pattern (; Resource: code) - no reason provided
Binding strengths differ (Pattern: example; ; Resource: required) - no reason provided
subject does not contain the recommended logical text for short (Pattern: Type of individual the defined service is for; ; Resource: Resource that can be subject of QuestionnaireResponse) - no reason provided
subject does not contain the recommended logical text for definition (Pattern: A code or group definition that describes the intended subject of instantiations of this definition.; ; Resource: The types of subjects that can be the subject of responses created for the questionnaire.) - no reason provided
subject does not contain the recommended logical text for requirements (Pattern: Many protocols, order sets and guidelines are intended for use only with specific types of patients or subjects.; ; Resource: Allows enforcing that a QuestionnaireResponse only has a .subject element of the appropriate type.) - no reason provided
|
Names are different.
Type Mismatch. |
|
|
| Definition.date |
| Definition.date : dateTime [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.date : dateTime [0..1]
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.date : dateTime [0..1]
|
|
|
|
| EventDefinition |
- EventDefinition.date : dateTime [0..1]
|
|
|
|
| Measure |
- Measure.date : dateTime [0..1]
|
|
|
|
| MessageDefinition |
- MessageDefinition.date : dateTime [1..1]
Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided
|
Cardinality Problem. |
|
|
| ObservationDefinition |
- ObservationDefinition.date : dateTime [0..1]
date does not contain the recommended logical text for definition (Pattern: The date (and optionally time) when the observation definition was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the observation definition changes.; ; Resource: The date (and optionally time) when the ObservationDefinition was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the ObservationDefinition changes.) - no reason provided
date does not contain the recommended logical text for comments (Pattern: The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the observation definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; ; Resource: The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the ObservationDefinition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
|
|
|
|
| OperationDefinition |
- OperationDefinition.date : dateTime [0..1]
|
|
|
|
| PlanDefinition |
- PlanDefinition.date : dateTime [0..1]
|
|
|
|
| Questionnaire |
- Questionnaire.date : dateTime [0..1]
|
|
|
|
| Requirements |
- Requirements.date : dateTime [0..1]
date does not contain the recommended logical text for definition (Pattern: The date (and optionally time) when the requirements was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the requirements changes.; ; Resource: The date (and optionally time) when the Requirements was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the Requirements changes.) - no reason provided
date does not contain the recommended logical text for comments (Pattern: The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the requirements. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; ; Resource: Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the Requirements. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.date : dateTime [0..1]
date does not contain the recommended logical text for short (Pattern: Date last changed; ; Resource: Date status first applied) - no reason provided
date does not contain the recommended logical text for definition (Pattern: The date (and optionally time) when the subscription topic was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the subscription topic changes.; ; Resource: The date (and optionally time) when the subscription topic was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the subscription topic changes.) - no reason provided
date does not contain the recommended logical text for comments (Pattern: The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the subscription topic. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; ; Resource: See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
|
|
|
|
| TestPlan |
- TestPlan.date : dateTime [0..1]
date does not contain the recommended logical text for definition (Pattern: The date (and optionally time) when the test plan was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the test plan changes.; ; Resource: The date (and optionally time) when the test plan was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the test plan changes.) - no reason provided
|
|
|
|
| TestScript |
- TestScript.date : dateTime [0..1]
date does not contain the recommended logical text for definition (Pattern: The date (and optionally time) when the test script was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the test script changes.; ; Resource: The date (and optionally time) when the test script was last significantly changed. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the test script changes.) - no reason provided
|
|
|
|
| Definition.publisher |
| Definition.publisher : string [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.publisher : string [0..1]
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.publisher : string [0..1]
|
|
|
|
| EventDefinition |
- EventDefinition.publisher : string [0..1]
|
|
|
|
| Measure |
- Measure.publisher : string [0..1]
|
|
|
|
| MessageDefinition |
- MessageDefinition.publisher : string [0..1]
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.publisher : string [0..1]
publisher does not contain the recommended logical text for short (Pattern: Name of the publisher/steward (organization or individual); ; Resource: The name of the individual or organization that published the ObservationDefinition) - no reason provided
publisher does not contain the recommended logical text for definition (Pattern: The name of the organization or individual responsible for the release and ongoing maintenance of the observation definition.; ; Resource: Helps establish the "authority/credibility" of the ObservationDefinition. May also allow for contact.) - no reason provided
publisher does not contain the recommended logical text for comments (Pattern: Usually an organization but may be an individual. The publisher (or steward) of the observation definition is the organization or individual primarily responsible for the maintenance and upkeep of the observation definition. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the observation definition. This item SHOULD be populated unless the information is available from context.; ; Resource: ) - no reason provided
publisher does not contain the recommended logical text for requirements (Pattern: Helps establish the "authority/credibility" of the observation definition. May also allow for contact.; ; Resource: Usually an organization, but may be an individual. The publisher (or steward) of the ObservationDefinition is the organization or individual primarily responsible for the maintenance and upkeep of the ObservationDefinition. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the ObservationDefinition. This item SHOULD be populated unless the information is available from context.) - no reason provided
|
|
|
|
| OperationDefinition |
- OperationDefinition.publisher : string [0..1]
|
|
|
|
| PlanDefinition |
- PlanDefinition.publisher : string [0..1]
|
|
|
|
| Questionnaire |
- Questionnaire.publisher : string [0..1]
|
|
|
|
| Requirements |
- Requirements.publisher : string [0..1]
publisher does not contain the recommended logical text for definition (Pattern: The name of the organization or individual responsible for the release and ongoing maintenance of the requirements.; ; Resource: The name of the organization or individual responsible for the release and ongoing maintenance of the Requirements.) - no reason provided
publisher does not contain the recommended logical text for comments (Pattern: Usually an organization but may be an individual. The publisher (or steward) of the requirements is the organization or individual primarily responsible for the maintenance and upkeep of the requirements. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the requirements. This item SHOULD be populated unless the information is available from context.; ; Resource: Usually an organization but may be an individual. The publisher (or steward) of the Requirements is the organization or individual primarily responsible for the maintenance and upkeep of the Requirements. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the Requirements. This item SHOULD be populated unless the information is available from context.) - no reason provided
publisher does not contain the recommended logical text for requirements (Pattern: Helps establish the "authority/credibility" of the requirements. May also allow for contact.; ; Resource: Helps establish the "authority/credibility" of the Requirements. May also allow for contact.) - no reason provided
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.publisher : string [0..1]
publisher does not contain the recommended logical text for short (Pattern: Name of the publisher/steward (organization or individual); ; Resource: The name of the individual or organization that published the SubscriptionTopic) - no reason provided
publisher does not contain the recommended logical text for definition (Pattern: The name of the organization or individual responsible for the release and ongoing maintenance of the subscription topic.; ; Resource: Helps establish the "authority/credibility" of the SubscriptionTopic. May also allow for contact.) - no reason provided
publisher does not contain the recommended logical text for comments (Pattern: Usually an organization but may be an individual. The publisher (or steward) of the subscription topic is the organization or individual primarily responsible for the maintenance and upkeep of the subscription topic. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the subscription topic. This item SHOULD be populated unless the information is available from context.; ; Resource: ) - no reason provided
publisher does not contain the recommended logical text for requirements (Pattern: Helps establish the "authority/credibility" of the subscription topic. May also allow for contact.; ; Resource: Usually an organization, but may be an individual. The publisher (or steward) of the SubscriptionTopic is the organization or individual primarily responsible for the maintenance and upkeep of the Topic. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the Topic. This item SHOULD be populated unless the information is available from context.) - no reason provided
|
|
|
|
| TestPlan |
- TestPlan.publisher : string [0..1]
|
|
|
|
| TestScript |
- TestScript.publisher : string [0..1]
|
|
|
|
| Definition.contact |
| Definition.contact : ContactDetail [0..*] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.contact : ContactDetail [0..*]
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.contact : ContactDetail [0..*]
|
|
|
|
| EventDefinition |
- EventDefinition.contact : ContactDetail [0..*]
|
|
|
|
| Measure |
- Measure.contact : ContactDetail [0..*]
|
|
|
|
| MessageDefinition |
- MessageDefinition.contact : ContactDetail [0..*]
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.contact : ContactDetail [0..*]
|
|
|
|
| OperationDefinition |
- OperationDefinition.contact : ContactDetail [0..*]
|
|
|
|
| PlanDefinition |
- PlanDefinition.contact : ContactDetail [0..*]
|
|
|
|
| Questionnaire |
- Questionnaire.contact : ContactDetail [0..*]
|
|
|
|
| Requirements |
- Requirements.contact : ContactDetail [0..*]
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.contact : ContactDetail [0..*]
|
|
|
|
| TestPlan |
- TestPlan.contact : ContactDetail [0..*]
|
|
|
|
| TestScript |
- TestScript.contact : ContactDetail [0..*]
|
|
|
|
| Definition.description |
| Definition.description : markdown [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.description : markdown [0..1]
description does not contain the recommended logical text for comments (Pattern: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the activity definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context.; ; Resource: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the activity definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the activity definition is presumed to be the predominant language in the place the activity definition was created).) - no reason provided
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.description : markdown [0..1]
description does not contain the recommended logical text for comments (Pattern: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the charge item definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context.; ; Resource: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the charge item definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the charge item definition is presumed to be the predominant language in the place the charge item definition was created).) - no reason provided
|
|
|
|
| EventDefinition |
- EventDefinition.description : markdown [0..1]
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
description does not contain the recommended logical text for comments (Pattern: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the event definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context.; ; Resource: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the event definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the event definition is presumed to be the predominant language in the place the event definition was created).) - no reason provided
|
|
|
|
| Measure |
- Measure.description : markdown [0..1]
description does not contain the recommended logical text for comments (Pattern: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the measure as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context.; ; Resource: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the measure as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the measure is presumed to be the predominant language in the place the measure was created).) - no reason provided
|
|
|
|
| MessageDefinition |
- MessageDefinition.description : markdown [0..1]
description does not contain the recommended logical text for comments (Pattern: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the message definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context.; ; Resource: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the message definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the message definition is presumed to be the predominant language in the place the message definition was created).) - no reason provided
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.description : markdown [0..1]
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
description does not contain the recommended logical text for short (Pattern: Natural language description of the observation definition; ; Resource: Natural language description of the ObservationDefinition) - no reason provided
description does not contain the recommended logical text for definition (Pattern: A free text natural language description of the observation definition from a consumer's perspective.; ; Resource: A free text natural language description of the ObservationDefinition from the consumer's perspective.) - no reason provided
description does not contain the recommended logical text for comments (Pattern: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the observation definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context.; ; Resource: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the module as conveyed in the text field of the resource itself. This item SHOULD be populated unless the information is available from context.) - no reason provided
|
|
|
|
| OperationDefinition |
- OperationDefinition.description : markdown [0..1]
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
description does not contain the recommended logical text for comments (Pattern: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the operation definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context.; ; Resource: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the operation definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the operation definition is presumed to be the predominant language in the place the operation definition was created).) - no reason provided
|
|
|
|
| PlanDefinition |
- PlanDefinition.description : markdown [0..1]
description does not contain the recommended logical text for comments (Pattern: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the plan definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context.; ; Resource: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the plan definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the plan definition is presumed to be the predominant language in the place the plan definition was created).) - no reason provided- PlanDefinition.action.description : markdown [0..1]
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
description does not contain the recommended logical text for short (Pattern: Natural language description of the plan definition; ; Resource: Brief description of the action) - no reason provided
description does not contain the recommended logical text for definition (Pattern: A free text natural language description of the plan definition from a consumer's perspective.; ; Resource: A brief description of the action used to provide a summary to display to the user.) - no reason provided
description does not contain the recommended logical text for comments (Pattern: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the plan definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context.; ; Resource: ) - no reason provided- PlanDefinition.action.textEquivalent : markdown [0..1]
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
description does not contain the recommended logical text for short (Pattern: Natural language description of the plan definition; ; Resource: Static text equivalent of the action, used if the dynamic aspects cannot be interpreted by the receiving system) - no reason provided
description does not contain the recommended logical text for definition (Pattern: A free text natural language description of the plan definition from a consumer's perspective.; ; Resource: A text equivalent of the action to be performed. This provides a human-interpretable description of the action when the definition is consumed by a system that might not be capable of interpreting it dynamically.) - no reason provided
description does not contain the recommended logical text for comments (Pattern: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the plan definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context.; ; Resource: ) - no reason provided
|
Names are different. |
|
|
| Questionnaire |
- Questionnaire.description : markdown [0..1]
|
|
|
|
| Requirements |
- Requirements.description : markdown [0..1]
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
description does not contain the recommended logical text for definition (Pattern: A free text natural language description of the requirements from a consumer's perspective.; ; Resource: A free text natural language description of the requirements.) - no reason provided
description does not contain the recommended logical text for comments (Pattern: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the requirements as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context.; ; Resource: This description can be used for a general description of the requirements, and which covers why it was defined.) - no reason provided
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.description : markdown [0..1]
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
description does not contain the recommended logical text for short (Pattern: Natural language description of the subscription topic; ; Resource: Natural language description of the SubscriptionTopic) - no reason provided
description does not contain the recommended logical text for definition (Pattern: A free text natural language description of the subscription topic from a consumer's perspective.; ; Resource: A free text natural language description of the Topic from the consumer's perspective.) - no reason provided
description does not contain the recommended logical text for comments (Pattern: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the subscription topic as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context.; ; Resource: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the module as conveyed in the text field of the resource itself. This item SHOULD be populated unless the information is available from context.) - no reason provided
|
|
|
|
| TestPlan |
- TestPlan.description : markdown [0..1]
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
description does not contain the recommended logical text for comments (Pattern: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the test plan as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context.; ; Resource: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the test plan as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the test plan is presumed to be the predominant language in the place the test plan was created).) - no reason provided
|
|
|
|
| TestScript |
- TestScript.description : markdown [0..1]
IsSummary differs (Pattern: true; ; Resource: false) - no reason provided
description does not contain the recommended logical text for comments (Pattern: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the test script as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context.; ; Resource: This description can be used to capture details such as comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the test script as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the test script is presumed to be the predominant language in the place the test script was created).) - no reason provided
|
|
|
|
| Definition.useContext |
| Definition.useContext : UsageContext [0..*] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.useContext : UsageContext [0..*]
useContext does not contain the recommended logical text for definition (Pattern: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate activity definitions.; ; Resource: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate activity definition instances.) - no reason provided
useContext does not contain the recommended logical text for comments (Pattern: When multiple useContexts are specified, there is no expectation that all or even any of the contexts apply.; ; Resource: When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.) - no reason provided
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.useContext : UsageContext [0..*]
useContext does not contain the recommended logical text for definition (Pattern: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate charge item definitions.; ; Resource: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate charge item definition instances.) - no reason provided
useContext does not contain the recommended logical text for comments (Pattern: When multiple useContexts are specified, there is no expectation that all or even any of the contexts apply.; ; Resource: When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.) - no reason provided
|
|
|
|
| EventDefinition |
- EventDefinition.useContext : UsageContext [0..*]
useContext does not contain the recommended logical text for definition (Pattern: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate event definitions.; ; Resource: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate event definition instances.) - no reason provided
useContext does not contain the recommended logical text for comments (Pattern: When multiple useContexts are specified, there is no expectation that all or even any of the contexts apply.; ; Resource: When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.) - no reason provided
|
|
|
|
| Measure |
- Measure.useContext : UsageContext [0..*]
useContext does not contain the recommended logical text for definition (Pattern: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate measures.; ; Resource: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate measure instances.) - no reason provided
useContext does not contain the recommended logical text for comments (Pattern: When multiple useContexts are specified, there is no expectation that all or even any of the contexts apply.; ; Resource: When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.) - no reason provided
|
|
|
|
| MessageDefinition |
- MessageDefinition.useContext : UsageContext [0..*]
useContext does not contain the recommended logical text for definition (Pattern: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate message definitions.; ; Resource: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate message definition instances.) - no reason provided
useContext does not contain the recommended logical text for comments (Pattern: When multiple useContexts are specified, there is no expectation that all or even any of the contexts apply.; ; Resource: When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.) - no reason provided
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.useContext : UsageContext [0..*]
useContext does not contain the recommended logical text for short (Pattern: The context that the content is intended to support; ; Resource: Content intends to support these contexts) - no reason provided
useContext does not contain the recommended logical text for definition (Pattern: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate observation definitions.; ; Resource: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate ObservationDefinition instances.) - no reason provided
useContext does not contain the recommended logical text for comments (Pattern: When multiple useContexts are specified, there is no expectation that all or even any of the contexts apply.; ; Resource: When multiple usageContexts are specified, there is no expectation for whether all or any of the contexts apply.) - no reason provided
|
|
|
|
| OperationDefinition |
- OperationDefinition.useContext : UsageContext [0..*]
useContext does not contain the recommended logical text for definition (Pattern: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate operation definitions.; ; Resource: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate operation definition.) - no reason provided
|
|
|
|
| PlanDefinition |
- PlanDefinition.useContext : UsageContext [0..*]
useContext does not contain the recommended logical text for definition (Pattern: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate plan definitions.; ; Resource: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate plan definition instances.) - no reason provided
useContext does not contain the recommended logical text for comments (Pattern: When multiple useContexts are specified, there is no expectation that all or even any of the contexts apply.; ; Resource: When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.) - no reason provided
|
|
|
|
| Questionnaire |
- Questionnaire.useContext : UsageContext [0..*]
|
|
|
|
| Requirements |
- Requirements.useContext : UsageContext [0..*]
useContext does not contain the recommended logical text for definition (Pattern: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate requirementss.; ; Resource: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate Requirements instances.) - no reason provided
useContext does not contain the recommended logical text for comments (Pattern: When multiple useContexts are specified, there is no expectation that all or even any of the contexts apply.; ; Resource: When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.) - no reason provided
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.useContext : UsageContext [0..*]
useContext does not contain the recommended logical text for short (Pattern: The context that the content is intended to support; ; Resource: Content intends to support these contexts) - no reason provided
useContext does not contain the recommended logical text for definition (Pattern: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate subscription topics.; ; Resource: The content was developed with a focus and intent of supporting the contexts that are listed. These terms may be used to assist with indexing and searching of code system definitions.) - no reason provided
useContext does not contain the recommended logical text for comments (Pattern: When multiple useContexts are specified, there is no expectation that all or even any of the contexts apply.; ; Resource: When multiple usageContexts are specified, there is no expectation for whether all or any of the contexts apply.) - no reason provided
|
|
|
|
| TestPlan |
- TestPlan.useContext : UsageContext [0..*]
useContext does not contain the recommended logical text for definition (Pattern: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate test plans.; ; Resource: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate test plan instances.) - no reason provided
useContext does not contain the recommended logical text for comments (Pattern: When multiple useContexts are specified, there is no expectation that all or even any of the contexts apply.; ; Resource: When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.) - no reason provided
|
|
|
|
| TestScript |
- TestScript.useContext : UsageContext [0..*]
useContext does not contain the recommended logical text for definition (Pattern: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate test scripts.; ; Resource: The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate test script instances.) - no reason provided
useContext does not contain the recommended logical text for comments (Pattern: When multiple useContexts are specified, there is no expectation that all or even any of the contexts apply.; ; Resource: When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.) - no reason provided
|
|
|
|
| Definition.jurisdiction |
| Definition.jurisdiction : CodeableConcept [0..*] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.jurisdiction : CodeableConcept [0..*]
jurisdiction does not contain the recommended logical text for comments (Pattern: It may be possible for the activity definition to be used in jurisdictions other than those for which it was originally designed or intended
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.).; ; Resource: It may be possible for the activity definition to be used in jurisdictions other than those for which it was originally designed or intended.
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)) - no reason provided
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.jurisdiction : CodeableConcept [0..*]
jurisdiction does not contain the recommended logical text for comments (Pattern: It may be possible for the charge item definition to be used in jurisdictions other than those for which it was originally designed or intended
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.).; ; Resource: It may be possible for the charge item definition to be used in jurisdictions other than those for which it was originally designed or intended.
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)) - no reason provided
|
|
|
|
| EventDefinition |
- EventDefinition.jurisdiction : CodeableConcept [0..*]
jurisdiction does not contain the recommended logical text for comments (Pattern: It may be possible for the event definition to be used in jurisdictions other than those for which it was originally designed or intended
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.).; ; Resource: It may be possible for the event definition to be used in jurisdictions other than those for which it was originally designed or intended.
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)) - no reason provided
|
|
|
|
| Measure |
- Measure.jurisdiction : CodeableConcept [0..*]
jurisdiction does not contain the recommended logical text for comments (Pattern: It may be possible for the measure to be used in jurisdictions other than those for which it was originally designed or intended
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.).; ; Resource: It may be possible for the measure to be used in jurisdictions other than those for which it was originally designed or intended.
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)) - no reason provided
|
|
|
|
| MessageDefinition |
- MessageDefinition.jurisdiction : CodeableConcept [0..*]
jurisdiction does not contain the recommended logical text for comments (Pattern: It may be possible for the message definition to be used in jurisdictions other than those for which it was originally designed or intended
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.).; ; Resource: It may be possible for the message definition to be used in jurisdictions other than those for which it was originally designed or intended.
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)) - no reason provided
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.jurisdiction : CodeableConcept [0..*]
jurisdiction does not contain the recommended logical text for short (Pattern: Intended jurisdiction for observation definition (if applicable); ; Resource: Intended jurisdiction for this ObservationDefinition (if applicable)) - no reason provided
jurisdiction does not contain the recommended logical text for definition (Pattern: A legal or geographic region in which the observation definition is intended to be used.; ; Resource: A jurisdiction in which the ObservationDefinition is intended to be used.) - no reason provided
jurisdiction does not contain the recommended logical text for comments (Pattern: It may be possible for the observation definition to be used in jurisdictions other than those for which it was originally designed or intended
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.).; ; Resource: It may be possible for the ObservationDefinition to be used in jurisdictions other than those for which it was originally designed or intended.
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)) - no reason provided
|
|
|
|
| OperationDefinition |
- OperationDefinition.jurisdiction : CodeableConcept [0..*]
jurisdiction does not contain the recommended logical text for comments (Pattern: It may be possible for the operation definition to be used in jurisdictions other than those for which it was originally designed or intended
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.).; ; Resource: It may be possible for the operation definition to be used in jurisdictions other than those for which it was originally designed or intended.
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)) - no reason provided
|
|
|
|
| PlanDefinition |
- PlanDefinition.jurisdiction : CodeableConcept [0..*]
jurisdiction does not contain the recommended logical text for comments (Pattern: It may be possible for the plan definition to be used in jurisdictions other than those for which it was originally designed or intended
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.).; ; Resource: It may be possible for the plan definition to be used in jurisdictions other than those for which it was originally designed or intended.
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)) - no reason provided
|
|
|
|
| Questionnaire |
- Questionnaire.jurisdiction : CodeableConcept [0..*]
jurisdiction does not contain the recommended logical text for comments (Pattern: It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.).; ; Resource: It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended.
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)) - no reason provided
|
|
|
|
| Requirements |
- Requirements.jurisdiction : CodeableConcept [0..*]
jurisdiction does not contain the recommended logical text for short (Pattern: Intended jurisdiction for requirements (if applicable); ; Resource: Intended jurisdiction for Requirements (if applicable)) - no reason provided
jurisdiction does not contain the recommended logical text for definition (Pattern: A legal or geographic region in which the requirements is intended to be used.; ; Resource: A legal or geographic region in which the Requirements is intended to be used.) - no reason provided
jurisdiction does not contain the recommended logical text for comments (Pattern: It may be possible for the requirements to be used in jurisdictions other than those for which it was originally designed or intended
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.).; ; Resource: It may be possible for the Requirements to be used in jurisdictions other than those for which it was originally designed or intended
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.).) - no reason provided
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.jurisdiction : CodeableConcept [0..*]
jurisdiction does not contain the recommended logical text for short (Pattern: Intended jurisdiction for subscription topic (if applicable); ; Resource: Intended jurisdiction of the SubscriptionTopic (if applicable)) - no reason provided
jurisdiction does not contain the recommended logical text for definition (Pattern: A legal or geographic region in which the subscription topic is intended to be used.; ; Resource: A jurisdiction in which the Topic is intended to be used.) - no reason provided
jurisdiction does not contain the recommended logical text for comments (Pattern: It may be possible for the subscription topic to be used in jurisdictions other than those for which it was originally designed or intended
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.).; ; Resource: DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)) - no reason provided
|
|
|
|
| TestPlan |
- TestPlan.jurisdiction : CodeableConcept [0..*]
jurisdiction does not contain the recommended logical text for short (Pattern: Intended jurisdiction for test plan (if applicable); ; Resource: Intended jurisdiction where the test plan applies (if applicable)) - no reason provided
jurisdiction does not contain the recommended logical text for comments (Pattern: It may be possible for the test plan to be used in jurisdictions other than those for which it was originally designed or intended
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.).; ; Resource: It may be possible for the test plan to be used in jurisdictions other than those for which it was originally designed or intended.
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)) - no reason provided
|
|
|
|
| TestScript |
- TestScript.jurisdiction : CodeableConcept [0..*]
jurisdiction does not contain the recommended logical text for comments (Pattern: It may be possible for the test script to be used in jurisdictions other than those for which it was originally designed or intended
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.).; ; Resource: It may be possible for the test script to be used in jurisdictions other than those for which it was originally designed or intended.
DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)) - no reason provided
|
|
|
|
| Definition.purpose |
| Definition.purpose : markdown [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.purpose : markdown [0..1]
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.purpose : markdown [0..1]
|
|
|
|
| EventDefinition |
- EventDefinition.purpose : markdown [0..1]
|
|
|
|
| Measure |
- Measure.purpose : markdown [0..1]
|
|
|
|
| MessageDefinition |
- MessageDefinition.purpose : markdown [0..1]
IsSummary differs (Pattern: false; ; Resource: true) - no reason provided
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.purpose : markdown [0..1]
purpose does not contain the recommended logical text for short (Pattern: Why this observation definition is defined; ; Resource: Why this ObservationDefinition is defined) - no reason provided
purpose does not contain the recommended logical text for definition (Pattern: Explanation of why this observation definition is needed and why it has been designed as it has.; ; Resource: Explains why this ObservationDefinition is needed and why it has been designed as it has.) - no reason provided
purpose does not contain the recommended logical text for comments (Pattern: This element does not describe the usage of the observation definition. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this observation definition.; ; Resource: This element does not describe the usage of the ObservationDefinition. Rather it is for traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this ObservationDefinition.) - no reason provided
|
|
|
|
| OperationDefinition |
- OperationDefinition.purpose : markdown [0..1]
|
|
|
|
| PlanDefinition |
- PlanDefinition.purpose : markdown [0..1]
|
|
|
|
| Questionnaire |
- Questionnaire.purpose : markdown [0..1]
|
|
|
|
| Requirements |
- Requirements.purpose : markdown [0..1]
purpose does not contain the recommended logical text for short (Pattern: Why this requirements is defined; ; Resource: Why this Requirements is defined) - no reason provided
purpose does not contain the recommended logical text for definition (Pattern: Explanation of why this requirements is needed and why it has been designed as it has.; ; Resource: Explanation of why this Requirements is needed and why it has been designed as it has.) - no reason provided
purpose does not contain the recommended logical text for comments (Pattern: This element does not describe the usage of the requirements. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this requirements.; ; Resource: This element does not describe the usage of the Requirements. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this Requirements.) - no reason provided
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.purpose : markdown [0..1]
purpose does not contain the recommended logical text for short (Pattern: Why this subscription topic is defined; ; Resource: Why this SubscriptionTopic is defined) - no reason provided
purpose does not contain the recommended logical text for definition (Pattern: Explanation of why this subscription topic is needed and why it has been designed as it has.; ; Resource: Explains why this Topic is needed and why it has been designed as it has.) - no reason provided
purpose does not contain the recommended logical text for comments (Pattern: This element does not describe the usage of the subscription topic. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this subscription topic.; ; Resource: This element does not describe the usage of the Topic. Rather it is for traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this Topic.) - no reason provided
|
|
|
|
| TestPlan |
- TestPlan.purpose : markdown [0..1]
purpose does not contain the recommended logical text for comments (Pattern: This element does not describe the usage of the test plan. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this test plan.; ; Resource: This element does not describe the usage of the test plan Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this test plan.) - no reason provided
|
|
|
|
| TestScript |
- TestScript.purpose : markdown [0..1]
|
|
|
|
| Definition.copyright |
| Definition.copyright : markdown [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.copyright : markdown [0..1]
copyright does not contain the recommended logical text for requirements (Pattern: Consumers of the activity definition must be able to determine any legal restrictions on the use of the artifact and/or its content.; ; Resource: Consumers must be able to determine any legal restrictions on the use of the activity definition and/or its content.) - no reason provided
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.copyright : markdown [0..1]
copyright does not contain the recommended logical text for requirements (Pattern: Consumers of the charge item definition must be able to determine any legal restrictions on the use of the artifact and/or its content.; ; Resource: Consumers must be able to determine any legal restrictions on the use of the charge item definition and/or its content.) - no reason provided
|
|
|
|
| EventDefinition |
- EventDefinition.copyright : markdown [0..1]
copyright does not contain the recommended logical text for requirements (Pattern: Consumers of the event definition must be able to determine any legal restrictions on the use of the artifact and/or its content.; ; Resource: Consumers must be able to determine any legal restrictions on the use of the event definition and/or its content.) - no reason provided
|
|
|
|
| Measure |
- Measure.copyright : markdown [0..1]
copyright does not contain the recommended logical text for requirements (Pattern: Consumers of the measure must be able to determine any legal restrictions on the use of the artifact and/or its content.; ; Resource: Consumers must be able to determine any legal restrictions on the use of the measure and/or its content.) - no reason provided
|
|
|
|
| MessageDefinition |
- MessageDefinition.copyright : markdown [0..1]
copyright does not contain the recommended logical text for requirements (Pattern: Consumers of the message definition must be able to determine any legal restrictions on the use of the artifact and/or its content.; ; Resource: Consumers must be able to determine any legal restrictions on the use of the message definition and/or its content.) - no reason provided
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.copyright : markdown [0..1]
copyright does not contain the recommended logical text for definition (Pattern: A copyright statement relating to the observation definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the observation definition.; ; Resource: Copyright statement relating to the ObservationDefinition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the ObservationDefinition.) - no reason provided
copyright does not contain the recommended logical text for requirements (Pattern: Consumers of the observation definition must be able to determine any legal restrictions on the use of the artifact and/or its content.; ; Resource: Consumers of the ObservationDefinition must be able to determine any legal restrictions on the use of the artifact and/or its content.) - no reason provided
|
|
|
|
| OperationDefinition |
- OperationDefinition.copyright : markdown [0..1]
|
|
|
|
| PlanDefinition |
- PlanDefinition.copyright : markdown [0..1]
copyright does not contain the recommended logical text for requirements (Pattern: Consumers of the plan definition must be able to determine any legal restrictions on the use of the artifact and/or its content.; ; Resource: Consumers must be able to determine any legal restrictions on the use of the plan definition and/or its content.) - no reason provided
|
|
|
|
| Questionnaire |
- Questionnaire.copyright : markdown [0..1]
|
|
|
|
| Requirements |
- Requirements.copyright : markdown [0..1]
copyright does not contain the recommended logical text for definition (Pattern: A copyright statement relating to the requirements and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the requirements.; ; Resource: A copyright statement relating to the Requirements and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the Requirements.) - no reason provided
copyright does not contain the recommended logical text for requirements (Pattern: Consumers of the requirements must be able to determine any legal restrictions on the use of the artifact and/or its content.; ; Resource: Consumers must be able to determine any legal restrictions on the use of the Requirements.) - no reason provided
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.copyright : markdown [0..1]
copyright does not contain the recommended logical text for definition (Pattern: A copyright statement relating to the subscription topic and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the subscription topic.; ; Resource: A copyright statement relating to the SubscriptionTopic and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the SubscriptionTopic.) - no reason provided
copyright does not contain the recommended logical text for requirements (Pattern: Consumers of the subscription topic must be able to determine any legal restrictions on the use of the artifact and/or its content.; ; Resource: Consumers of the TSubscriptionTopicopic must be able to determine any legal restrictions on the use of the artifact and/or its content.) - no reason provided
|
|
|
|
| TestPlan |
- TestPlan.copyright : markdown [0..1]
copyright does not contain the recommended logical text for requirements (Pattern: Consumers of the test plan must be able to determine any legal restrictions on the use of the artifact and/or its content.; ; Resource: Consumers must be able to determine any legal restrictions on the use of the test plan and/or its content.) - no reason provided
|
|
|
|
| TestScript |
- TestScript.copyright : markdown [0..1]
copyright does not contain the recommended logical text for requirements (Pattern: Consumers of the test script must be able to determine any legal restrictions on the use of the artifact and/or its content.; ; Resource: Consumers must be able to determine any legal restrictions on the use of the test script and/or its content.) - no reason provided
|
|
|
|
| Definition.copyrightLabel |
| Definition.copyrightLabel : string [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.copyrightLabel : string [0..1]
|
|
|
|
| EventDefinition |
- EventDefinition.copyrightLabel : string [0..1]
|
|
|
|
| Measure |
- Measure.copyrightLabel : string [0..1]
|
|
|
|
| OperationDefinition |
- OperationDefinition.copyrightLabel : string [0..1]
|
|
|
|
| PlanDefinition |
- PlanDefinition.copyrightLabel : string [0..1]
|
|
|
|
| Questionnaire |
- Questionnaire.copyrightLabel : string [0..1]
|
|
|
|
| Requirements |
- Requirements.copyrightLabel : string [0..1]
|
|
|
|
| Definition.approvalDate |
| Definition.approvalDate : date [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.approvalDate : date [0..1]
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.approvalDate : date [0..1]
|
|
|
|
| EventDefinition |
- EventDefinition.approvalDate : date [0..1]
IsSummary differs (Pattern: false; ; Resource: true) - no reason provided
|
|
|
|
| Measure |
- Measure.approvalDate : date [0..1]
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.approvalDate : date [0..1]
approvalDate does not contain the recommended logical text for short (Pattern: When the observation definition was approved by publisher; ; Resource: When ObservationDefinition was approved by publisher) - no reason provided
approvalDate does not contain the recommended logical text for definition (Pattern: The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage.; ; Resource: The date on which the asset content was approved by the publisher. Approval happens once when the content is officially approved for usage.) - no reason provided
approvalDate does not contain the recommended logical text for comments (Pattern: The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; ; Resource: The date may be more recent than the approval date because of minor changes / editorial corrections.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
|
|
|
|
| PlanDefinition |
- PlanDefinition.approvalDate : date [0..1]
|
|
|
|
| Questionnaire |
- Questionnaire.approvalDate : date [0..1]
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.approvalDate : date [0..1]
approvalDate does not contain the recommended logical text for short (Pattern: When the subscription topic was approved by publisher; ; Resource: When SubscriptionTopic is/was approved by publisher) - no reason provided
approvalDate does not contain the recommended logical text for definition (Pattern: The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage.; ; Resource: The date on which the asset content was approved by the publisher. Approval happens once when the content is officially approved for usage.) - no reason provided
approvalDate does not contain the recommended logical text for comments (Pattern: The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; ; Resource: The date may be more recent than the approval date because of minor changes / editorial corrections.) - no reason provided
|
|
|
|
| Definition.lastReviewDate |
| Definition.lastReviewDate : date [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.lastReviewDate : date [0..1]
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.lastReviewDate : date [0..1]
|
|
|
|
| EventDefinition |
- EventDefinition.lastReviewDate : date [0..1]
IsSummary differs (Pattern: false; ; Resource: true) - no reason provided
|
|
|
|
| Measure |
- Measure.lastReviewDate : date [0..1]
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.lastReviewDate : date [0..1]
lastReviewDate does not contain the recommended logical text for short (Pattern: When the observation definition was last reviewed; ; Resource: Date on which the asset content was last reviewed by the publisher) - no reason provided
lastReviewDate does not contain the recommended logical text for definition (Pattern: The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date.; ; Resource: The date on which the asset content was last reviewed. Review happens periodically after that, but doesn't change the original approval date.) - no reason provided
lastReviewDate does not contain the recommended logical text for comments (Pattern: If specified, this date follows the original approval date.; ; Resource: If specified, this is usually after the approval date.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
lastReviewDate does not contain the recommended logical text for requirements (Pattern: Gives a sense of how "current" the content is. Resources that have not been reviewed in a long time may have a risk of being less appropriate/relevant.; ; Resource: ) - no reason provided
|
|
|
|
| PlanDefinition |
- PlanDefinition.lastReviewDate : date [0..1]
|
|
|
|
| Questionnaire |
- Questionnaire.lastReviewDate : date [0..1]
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.lastReviewDate : date [0..1]
lastReviewDate does not contain the recommended logical text for short (Pattern: When the subscription topic was last reviewed; ; Resource: Date the Subscription Topic was last reviewed by the publisher) - no reason provided
lastReviewDate does not contain the recommended logical text for definition (Pattern: The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date.; ; Resource: The date on which the asset content was last reviewed. Review happens periodically after that, but doesn't change the original approval date.) - no reason provided
lastReviewDate does not contain the recommended logical text for comments (Pattern: If specified, this date follows the original approval date.; ; Resource: If specified, this is usually after the approval date.) - no reason provided
lastReviewDate does not contain the recommended logical text for requirements (Pattern: Gives a sense of how "current" the content is. Resources that have not been reviewed in a long time may have a risk of being less appropriate/relevant.; ; Resource: ) - no reason provided
|
|
|
|
| Definition.effectivePeriod |
| Definition.effectivePeriod : Period [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| ActivityDefinition |
- ActivityDefinition.effectivePeriod : Period [0..1]
effectivePeriod does not contain the recommended logical text for comments (Pattern: The effective period for a activity definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; ; Resource: The effective period for an activity definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a activity intended to be used for the year 2016 might be published in 2015.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
|
|
|
|
| ChargeItemDefinition |
- ChargeItemDefinition.applicability.effectivePeriod : Period [0..1]
|
|
|
|
| EventDefinition |
- EventDefinition.effectivePeriod : Period [0..1]
effectivePeriod does not contain the recommended logical text for comments (Pattern: The effective period for a event definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; ; Resource: The effective period for an event definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a definition intended to be used for the year 2016 might be published in 2015.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
|
|
|
|
| Measure |
- Measure.effectivePeriod : Period [0..1]
effectivePeriod does not contain the recommended logical text for comments (Pattern: The effective period for a measure determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; ; Resource: The effective period for a measure determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
|
|
|
|
| ObservationDefinition |
- ObservationDefinition.effectivePeriod : Period [0..1]
effectivePeriod does not contain the recommended logical text for short (Pattern: When the observation definition is expected to be used; ; Resource: The effective date range for the ObservationDefinition) - no reason provided
effectivePeriod does not contain the recommended logical text for definition (Pattern: The period during which the observation definition content was or is planned to be in active use.; ; Resource: The period during which the ObservationDefinition content was or is planned to be effective.) - no reason provided
effectivePeriod does not contain the recommended logical text for comments (Pattern: The effective period for a observation definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; ; Resource: The effective period for an ObservationDefinition determines when the content is applicable for usage and is independent of publication and review dates. For example, an observation definition intended to be used for the year 2021 might be published in 2020.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
effectivePeriod does not contain the recommended logical text for requirements (Pattern: Allows establishing a transition before a resource comes into effect and also allows for a sunsetting process when new versions of the observation definition are or are expected to be used instead.; ; Resource: ) - no reason provided
|
|
|
|
| PlanDefinition |
- PlanDefinition.effectivePeriod : Period [0..1]
effectivePeriod does not contain the recommended logical text for comments (Pattern: The effective period for a plan definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; ; Resource: The effective period for a plan definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a plan definition intended to be used for the year 2016 might be published in 2015.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
|
|
|
|
| Questionnaire |
- Questionnaire.effectivePeriod : Period [0..1]
effectivePeriod does not contain the recommended logical text for comments (Pattern: The effective period for a questionnaire determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; ; Resource: The effective period for a questionnaire determines when the content is applicable for usage and is independent of publication and review dates. For example, a questionnaire intended to be used for the year 2016 might be published in 2015.
See guidance around (not) making local changes to elements [here](canonicalresource.html#localization).) - no reason provided
|
|
|
|
| SubscriptionTopic |
- SubscriptionTopic.effectivePeriod : Period [0..1]
effectivePeriod does not contain the recommended logical text for short (Pattern: When the subscription topic is expected to be used; ; Resource: The effective date range for the SubscriptionTopic) - no reason provided
effectivePeriod does not contain the recommended logical text for definition (Pattern: The period during which the subscription topic content was or is planned to be in active use.; ; Resource: The period during which the SubscriptionTopic content was or is planned to be effective.) - no reason provided
effectivePeriod does not contain the recommended logical text for comments (Pattern: The effective period for a subscription topic determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; ; Resource: The effective period for a SubscriptionTopic determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 would be published in 2015.) - no reason provided
effectivePeriod does not contain the recommended logical text for requirements (Pattern: Allows establishing a transition before a resource comes into effect and also allows for a sunsetting process when new versions of the subscription topic are or are expected to be used instead.; ; Resource: ) - no reason provided
|
|
|
|
| Definition.topic |
| Definition.topic : CodeableConcept [0..*] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| Definition.performerType |
| Definition.performerType : CodeableConcept [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| Definition.code |
| Definition.code : CodeableConcept [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
| OperationDefinition |
- OperationDefinition.code : code [1..1]
Minimum Cardinality differs (Pattern: 0; ; Resource: 1) - no reason provided
Resource does not support types that are part of the pattern (Pattern: CodeableConcept) - no reason provided
Resource supports types that are not part of the pattern (; Resource: code) - no reason provided
code does not contain the recommended logical text for short (Pattern: Service to be done; ; Resource: Recommended name for operation in search url) - no reason provided
code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action that was or is being performed.; ; Resource: The label that is recommended to be used in the URL for this operation. In some cases, servers may need to use a different CapabilityStatement operation.name to differentiate between multiple SearchParameters that happen to have the same code.) - no reason provided
|
Type Mismatch.
Cardinality Problem. |
|
|
| Questionnaire |
- Questionnaire.code : Coding [0..*]
Maximum Cardinality differs (Pattern: 1; ; Resource: *) - no reason provided
Resource does not support types that are part of the pattern (Pattern: CodeableConcept) - no reason provided
Resource supports types that are not part of the pattern (; Resource: Coding) - no reason provided
Only one element has bindings (Pattern: false; ; Resource: true) - no reason provided
code does not contain the recommended logical text for short (Pattern: Service to be done; ; Resource: Concept that represents the overall questionnaire) - no reason provided
code does not contain the recommended logical text for definition (Pattern: A code that identifies the specific service or action that was or is being performed.; ; Resource: An identifier for this collection of questions in a particular terminology such as LOINC.) - no reason provided
|
Type Mismatch.
Cardinality Problem. |
|
|
| Definition.product |
| Definition.product : CodeableReference(BiologicallyDerivedProduct|DeviceDefinition|Medication|NutritionProduct|Substance) [0..1] |
| Resource |
Matches |
Issues |
Tasks |
Status |
Notes |
Workflow
|
Propose a change