Primary Care
current 
dft-preBallot - This is the first draft of the P-Care IG. For a full list of available versions, see the Directory of published versions
Coding
Links
Profile
Derived from
http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/coding-ca-core
Examples
Description
A reference to a code defined by a terminology system.
References to this resource
Resource Content
--- We have skipped the narrative for better readability of the resource ---
</text>
<baseDefinition value="http://fhir.infoway-inforoute.ca/cacore/StructureDefinition/coding-ca-core" />
</extension>
<comment value="Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information." />
</base>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</extension>
<definition value="The identification of the code system that defines the meaning of the symbol in the code." />
<comment value="The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged." />
<comment value="Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</extension>
<definition value="A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination)." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</extension>
<definition value="A representation of the meaning of the code in the system, following the rules of the system." />
<requirements value="Need to be able to carry a human-readable meaning of the code for readers that do not know the system." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</mapping>
</element>
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
</base>
</extension>
</extension>
</type>
</element>
<definition value="Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays)." />
<comment value="Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely." />
<requirements value="This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
<map value="fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]" />
</mapping>
</element>
</snapshot>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</element>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</element>
</extension>
</extension>
</extension>
</extension>
</extension>
<valueMarkdown value="P-Care server population, persistence, and acceptance requirements for this element." />
</extension>
</extension>
</extension>
</element>
</element>
</differential>
</StructureDefinition>
{
--- We have skipped the narrative for better readability of the resource ---
},
{
}
],
{
"comment": "Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.",
},
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
"ele-1"
],
{
},
{
}
],
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
"definition": "The identification of the code system that defines the meaning of the symbol in the code.",
"comment": "The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
"definition": "The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.",
"comment": "Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
"definition": "A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
{
},
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
},
{
}
],
}
],
"definition": "A representation of the meaning of the code in the system, following the rules of the system.",
"requirements": "Need to be able to carry a human-readable meaning of the code for readers that do not know the system.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
}
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
"ele-1"
],
{
},
{
}
],
]
},
{
},
],
"ele-1"
],
{
},
{
}
],
]
},
{
"xmlAttr"
],
},
{
{
},
{
}
],
}
],
},
{
"definition": "Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).",
"comment": "Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.",
"requirements": "This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.",
},
],
"ele-1"
],
{
}
],
{
},
{
},
{
},
{
"map": "fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\\#true a [ fhir:source \"true\"; fhir:target dt:CDCoding.codingRationale\\#O ]"
}
]
}
]
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
},
{
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
},
{
{
},
{
{
},
{
},
{
},
{
},
{
"valueMarkdown": "P-Care server population, persistence, and acceptance requirements for this element."
},
{
}
],
}
],
},
{
}
]
}
}
Constraints
Obligations
| Element | Actor | Code |
|---|---|---|
| code | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHOULD:persist, SHALL:no-error |
| display | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHOULD:persist, SHALL:no-error |
| system | http://fhir.infoway-inforoute.ca/p-care/ActorDefinition/pcare-server | SHALL:populate, SHOULD:persist, SHALL:no-error |