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 "Generated Narrative
target: Generated Summary: language: en; url: http://terminology.hl7.org/CodeSystem/v3-ActCode; id: urn:oid:2.16.840.1.113883.5.4; version: 2.1.0; name: ActCode; title: ActCode; status: active; date: 2019-12-15; 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
occurred: ?? --> 3 Aug. 2000, 3:28:56 pm
recorded: 1 Jan. 2010, 1:00:00 pm
reason: Originated prior to this dateTime; exact date not available.
activity: create
agent
type: Author
who: Woody Beeler
agent
type: Custodian
who: MnM WG