a fhir:Provenance;
fhir:Resource.id [ fhir:value "hx1c-v3-ActCode-cs-1-0-1"];
fhir:DomainResource.text [
fhir:Narrative.status [ fhir:value "generated" ];
fhir:Narrative.div "This provenance relates to Generated Summary: id: v3-ActCode; language: en; url: http://terminology.hl7.org/CodeSystem/v3-ActCode; urn:oid:2.16.840.1.113883.5.4; version: 2.0.0; name: ActCode; title: ActCode; status: active; date: Mar 20, 2019, 12:00:00 AM; publisher: Health Level 7; Health Level Seven: ; description: A code specifying the particular kind of Act that the Act-instance represents within its class.\r\n\r\n*Constraints:* The kind of Act (e.g. physical examination, serum potassium, inpatient encounter, charge financial transaction, etc.) is specified with a code from one of several, typically external, coding systems. The coding system will depend on the class of Act, such as LOINC for observations, etc.\r\n\r\nConceptually, the Act.code must be a specialization of the Act.classCode. This is why the structure of ActClass domain should be reflected in the superstructure of the ActCode domain and then individual codes or externally referenced vocabularies subordinated under these domains that reflect the ActClass structure.\r\n\r\nAct.classCode and Act.code are not modifiers of each other but the Act.code concept should really imply the Act.classCode concept. For a negative example, it is not appropriate to use an Act.code \"potassium\" together with and Act.classCode for \"laboratory observation\" to somehow mean \"potassium laboratory observation\" and then use the same Act.code for \"potassium\" together with Act.classCode for \"medication\" to mean \"substitution of potassium\". This mutually modifying use of Act.code and Act.classCode is not permitted.; hierarchyMeaning: is-a; content: complete
Summary
| Occurrence | ?? --> Aug 3, 2000, 1:28:56 AM |
| Recorded | Dec 31, 2009, 9:00:00 PM |
| Activity | create |
Agents
| type | who |
| Author | Woody Beeler |
| Custodian | MnM WG |
This provenance relates to Generated Summary: id: v3-ActClass; language: en; url: http://terminology.hl7.org/ValueSet/v3-ActClass; urn:oid:2.16.840.1.113883.1.11.11527; version: 2.0.0; name: ActClass; title: ActClass; status: active; date: Mar 26, 2014, 12:00:00 AM; description: A code specifying the major type of Act that this Act-instance represents.\r\n\r\n*Constraints:* The classCode domain is a tightly controlled vocabulary, not an external or user-defined vocabulary.\r\n\r\nEvery Act-instance must have a classCode. If the act class is not further specified, the most general Act.classCode (ACT) is used.\r\n\r\nThe Act.classCode must be a generalization of the specific Act concept (e.g., as expressed in Act.code), in other words, the Act concepts conveyed in an Act must be specializations of the Act.classCode. Especially, Act.code is not a \"modifier\" that can alter the meaning of a class code. (See Act.code for contrast.); immutable
Summary
| Occurrence | ?? --> Aug 3, 2000, 1:28:56 AM |
| Recorded | Dec 31, 2009, 9:00:00 PM |
| Activity | create |
Agents
| type | who |
| Author | Woody Beeler |
| Custodian | MnM WG |