# cwm conversion from http://www.ics.mq.edu.au/~borgun/RIM-HL7All.zip # PxButton | check with euler | bash .euler rim.n3 inconsistent.n3 #Processed by Id: cwm.py,v 1.165 2004/11/19 01:58:39 syosi Exp # using base file:/2004/acw/rim/ # Notation3 generation by # notation3.py,v 1.171 2004/12/28 03:29:21 syosi Exp # Base was: file:/2004/acw/rim/ @prefix : . @prefix a: . @prefix kb: . @prefix rdf: . kb:AD a :Class; :comment """The postal and residential address data type is used to communicate mailing and home or office addresses. The main use of such data is to allow printing mail labels (postal address), or to allow a person to physically visit that address (residential address). For example, a post box address is a postal address but not a residential address. Most residential addresses are also postal addresses. The residential address is not supposed to be a container for additional information that might be useful for finding geographic locations (e.g., GPS coordinates) or for performing epidemiological studies. Only those parts of addresses that are conventional for designating mailboxes or home or office addresses are part of the address data type. The postal and residential address data type is essentially a sequence of address part values, but adds to this a "use" code for information about when and if the address can be used for a given purpose. The property "formatted" has a character string value with the address formatted in lines and with proper spacing.Remember that semantic properties are bare of all control flow semantics. The property formatted could be implemented as a "procedure" that would "return" the formatted address, but it would not usually be a variable to which one could assign a formatted address. However, HL7 does not define applications but only the semantics of exchanged data values. Hence, the semantic model abstracts from concepts like "procedure", "return", and "assignment" but speaks only of property and value."""; :label "AD"; :subClassOf . a rdf:Property; a:maxCardinality "1"; a:values , , , , ; :comment """The address use code is a set of indicators what a given address is to be used for. Examples include residential address (RES, to visit), postal address (PST, to send mail), temporary address (TMP), birth address (BRT), and bad address (BAD, useless address kept for the record.) An address without specific use code might be a default address useful for any purpose, but an address with a specific use code would be preferred for that respective purpose."""; :domain kb:AD; :label "AD.use"; :range . kb:ADXP a :Class; :comment """An address part is essentially a character string that may have a type-tag signifying it�s role in the address. Typical parts that exist in about every address are street, house number, or post box, ZIP code, city, country but other roles may be defined regionally, nationally, or on an enterprise level (e.g. in military addresses). Addresses are usually broken up into lines, which is indicated by special line-break tokens. Addresses are conceptualized as text with added mark-up. The mark-up breaks the address into lines and describes the role of each address part if it is known. Address parts occur in the address in the order in which they would be printed on a mailing label. The model is similar to HTML or XML markup of text."""; :label "ADXP"; :subClassOf kb:ST . kb:ANT a :Class; :comment """Annotated is a generic data type extension supporting arbitrary free-text annotations (note) for any value of type T. The data type of the note property is CE, meaning that the note may be free text (usually) or may alternatively be coded. Note that annotations are annotations of specific values. It is improper use of annotations to tag information to values which belong to another structure. For example, �specimen hemolyzed� is a property of a specimen, not of an observation value, and yet, in HL7 v2.x it was common to send this as an annotation to the observation segment. Annotations must not be used when there are methods defined that are more robust. In HL7 v2.x installations, there has been a great number of annotations, about reference ranges or interpretation of values, recommendations, and more. In HL7 v3 most of this can � and must � be communicated in properly defined data structures. For example, recommendations may be treated as Service recommendation objects. Knowledge about interpretation can be presented in a defined text attribute, or as detailed knowledge structures. Another problematic example is the utterance �forwarded to reference lab.� This is likely not an annotation of any specific data attribute, but rather a complex statement about the specimen or an order. However, this is an interesting case that may or may not be covered by properly standardized HL7-structures. What this shows is that such cases should be brought to the attention of the standards committee rather than hidden in some code tagged to a data value to which it doesn�t belong. In general, annotations should be used sparingly � almost never on a routine basis �, or else are an indication for a use case that should be given proper attention in the information model. The domain of annotation notes can not be defined or circumscribed; every concept could potentially be used as an annotation. Therefore, coded annotations are very likely to be non-standardized and non-interoperable. HL7 does not define a standard domain of coded annotations. In the HL7 methodology, the use cases and information requirements are explicitly modeled as well defined data elements. Instead of using coded annotations, HL7 users and implementers should reuse this same HL7 methodology to extend the standard, e.g., adding new classes, fields, messages, etc. Such extended messages are not standard HL7 messages, but are still clearer and better than lengthy tables of coded annotations; furthermore HL7 extensions may be fed into the HL7 standardization process. Coded annotations should therefore be only used casually and temporary, to provide immediate remedy to an urgent business need, never to define long-lasting solutions."""; :label "ANT"; :subClassOf kb:T . a rdf:Property; a:maxCardinality "1"; :domain kb:ANT; :label "ANT.note"; :range kb:CE . kb:ANY a :Class; a:role "abstract"; :comment "The type DataValue defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type."; :label "ANY"; :subClassOf :Resource . a rdf:Property; a:maxCardinality "1"; a:values ; :comment "Every data value is of a data type. The data value implicitly carries the information about its own type. Thus, given a data value in an HL7 message, one can inquire about its data type. However, one cannot change the data type of a data value simple by changing this type property. conversions.)"; :domain kb:ANY; :label "ANY.dataType"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; a:values ; :comment """A property can be of an exceptional value. Exceptional values express missing information and possi-bly the reason why the information is missing. Exceptional values are also called NULL-values, and the exception is called the "flavor" of NULL. Thus, every data value is either a proper value or it is it NULL. If the value is NULL, the nullFlavor property is non-NULL. If the value is not NULL, its null flavor attribute is NULL (not applicable.) When a property, RIM attribute, or message field is called mandatory this means that any non-NULL value of the type to which the property belongs must have a non-NULL value for that property. In other HL7 specification the term "mandatory" is used while this specification formulates the mandatory con-straint explicitly."""; :domain kb:ANY; :label "ANY.nullFlavor"; :range kb:CS . kb:Access a :Class; :comment """A role played by a device when the device is used to administer therapeutic agents (medication and vital elements) into the body, or to drain material (e.g., exudates, pus, urine, air, blood) out of the body. For the most part, anything that would be used for access would be a device (something specifically manufactured or created to serve that purpose). Typically the device is a catheter or cannula inserted into a compartment of the body. A device enters the body from an anatomic site designated by the approach_site_cd. The body compartment into which material is administered or from which it is drained is designated by the target_site_cd. Note that the Access role primarily exists in order to describe material actually deployed as an access, and not so much the fresh material as it comes from the manufacturer. For example, in supply ordering a box of catheters from a distributor, it is not necessary to use the Access role class, since the material attributes will usually suffice to describe and identify the product for the order. But the Access role is used to communicate about the maintenance, intake/outflow, and due replacement of tubes and drains. Devices in the role of an Access are typically used in intake/outflow observations, and in medication routing instructions. Microbiologic observations on the material itself or on fluids coming out of a drain, are also common. OpenIssue: Issue relates to the restriction of access device to persons or animals as patients. In the case where the material desired does not originate from a "living subject" such as in environmental monitoring, then the access device definition needs to reflect that change. For example, an order for a sample to be taken from the clean-out port of a food processing device for a public health investigation."""; :label "Access"; :subClassOf kb:Role . a rdf:Property; a:maxCardinality "1"; :comment """Specifies the anatomic site where the line or drain first enters the body. For example in a arteria pulmonalis catheter targets a pulmonary artery but the access approach site is typically the vena carotis interna at the neck, or the vena subclavia at the fossa subclavia. The coding system is the same as for Procedure.access_site_cd., indeed the Access.approach_site_cd has been copied from the Procedure class into the Access role class. The value of the Access.approach_site_cd should be identical to the value of the Procedure.approach_site_cd of an associated access placement procedure. This attribute is used if such an associated access placement procedure is not communicated. Since accesses are typically placed for a considerable period of time and since the access is used as a resource of many acts, the access approach site becomes an important identifying attribute of the access itself."""; :domain kb:Access; :label "Access.approach_site_cd"; :range kb:CD . a rdf:Property; a:maxCardinality "1"; :comment "The gauge of an access is a measure for the inner diameter of the tube (the lumen.) Typically catheter gauge is measured in terms of units not seen elsewhere. Those units are defined in the Unified Code for Units of Measure."; :domain kb:Access; :label "Access.gauge_qty"; :range kb:PQ . a rdf:Property; a:maxCardinality "1"; :comment """This is the target site of the access, i.e., the compartment into which material is administered or from which it is collected. For example, a pulmonary artery catheter will have the target site arteria pulmonalis with or without a known laterality. For environmental testing this could be the incubation chamber or the cooling tower or the overflow reservoir, etc. The coding system is the same as for Procedure.target_site_cd; indeed the Access.target_site_cd has been copied from the Procedure class into the Access role class. The value of the Access.target_site_cd should be identical to the value of the Procedure.target_site_cd of an associated access placement procedure. This attribute is used if such an associated access placement procedure is not communicated. Since accesses are typically placed for a considerable period of time and since the access is used as a resource of many acts, the target site becomes an important identifying attribute of the access itself. The target site is an important information that determines what kinds of substances may or may not administered (e.g., special care to avoid medication injections into an arterial access.) OpenIssue: This is another area where the definition could be generalized to Entities other than Living_subjects. The target site for environmental sampling may be a particular part of a machine, sewage system, distribution system, etc."""; :domain kb:Access; :label "Access.target_site_cd"; :range kb:CD . kb:Account a :Class; :comment "A sub-class of Act representing a financial account established to track the net result of financial acts. Can be used to represent the accumulated total of billable amounts for goods or services received, payments made for goods or services, and debit and credit accounts between which financial transactions flow."; :label "Account"; :subClassOf kb:Financial_act . a rdf:Property; a:maxCardinality "1"; :comment "An interval describing the minimum and maximum allowed balances for an account."; :domain kb:Account; :label "Account.allowed_balance_qty"; :range . a rdf:Property; a:maxCardinality "1"; :comment """Indicates the currency that the account is managed in. ExtRef: ISO:4217"""; :domain kb:Account; :label "Account.currency_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment """A ratio that indicates the rate of interest that the account balance is subject to, and the term over which the interest rate compounds. Constraint: Unit of the denominator PQ datatype must be comparable to seconds. (I.e. the denominator must be measured in time.)"""; :domain kb:Account; :label "Account.interest_rate_qty"; :range . a rdf:Property; a:maxCardinality "1"; :comment "The descriptive name of the account as carried in the ledger of which the account is a part."; :domain kb:Account; :label "Account.nm"; :range kb:ST . kb:Acknowledgement a :Class; :comment "The Acknowledgement class contains information sent when acknowledging another message."; :label "Acknowledgement"; :subClassOf kb:HL7RIM . a rdf:Property; a:maxCardinality "1"; a:values , , , , , , , , , , , , ; :comment "This attribute allows for a coded error type."; :domain kb:Acknowledgement; :label "Acknowledgement.error_detail_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment "This attribute is used in the sequence number protocol."; :domain kb:Acknowledgement; :label "Acknowledgement.expected_sequence_nbr"; :range kb:INT . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid1015"; :domain kb:Acknowledgement; :label "Acknowledgement.has"; :range kb:Message . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid1011"; :domain kb:Acknowledgement; :label "Acknowledgement.is_acknowledged_by"; :range kb:Message . a rdf:Property; a:maxCardinality "1"; :comment "This attribute further describes an error condition. This text may be printed in error logs or presented to an end user."; :domain kb:Acknowledgement; :label "Acknowledgement.note_txt"; :range kb:ED . a rdf:Property; a:maxCardinality "1"; a:values , , , , ; :comment "This attribute contains an acknowledgement code as described in the HL7 message processing rules."; :domain kb:Acknowledgement; :label "Acknowledgement.type_cd"; :range kb:CS . kb:AcknowledgementCondition a :Class; :label "AcknowledgementCondition"; :subClassOf kb:HL7VocabularyConcept . kb:AcknowledgementType a :Class; :label "AcknowledgementType"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "AcknowledgementType.AA"; :subClassOf kb:AcknowledgementType . a kb:CS; ; :label "AcknowledgementType.AE"; :subClassOf kb:AcknowledgementType . a kb:CS; ; :label "AcknowledgementType.AR"; :subClassOf kb:AcknowledgementType . a kb:CS; ; :label "AcknowledgementType.CA"; :subClassOf kb:AcknowledgementType . a kb:CS; ; :label "AcknowledgementType.CE"; :subClassOf kb:AcknowledgementType . kb:Act a :Class; :comment """An action of interest that has happened, can happen, is happening, is intended to happen, or is requested/demanded to happen. An act is an intentional action in the business domain of HL7. Healthcare (and any profession or business) is constituted of intentional actions. An Act instance is a record of such an intentional action. Any intentional action can exist in different "moods". Moods describe activities as they progress in the business cycle, from defined, through planned and ordered to complete. Any instance of an Act assumes one and only one mood and will not change its mood along its life cycle. The moods - definition, intent, order, event - seem to specify a life cycle of an activity. However, the participants in the activity in these different moods are different, as is the data. Therefore, the mood of an Act instance is static. The progression actualization (i.e., the progression from defined, through planned and ordered, to being performed) is called the "business cycle" to distinguish it from the "life cycle" of a single act instance. Related Act instances that form such a "business cycle" are linked through the Act_relationship class. Examples for acts in health care are: a clinical test, an assessment of health condition (such as problems and diagnoses), the setting of healthcare goals, the performance of treatment services (such as medication, surgery, physical and psychological therapy), assisting, monitoring or attending, training and education services to patients and their next of kin, and notary services (such as advanced directives or living will). Acts have participants, which can be actors or targets. Examples of actors are nurses, doctors, family members, notary publics, and service organizations -- every person or organization that is capable of independent decisions and can thus is responsible (and liable) for the actions performed. Target participants in an act may include the patient, the patient's spouse, family, or community, a specimen drawn from the patient or from any object of interest. As patients do play active roles in their own healthcare, the patient can be both an active participant and a target participant at the same time (self-administered or reflexive services.) An act can have multiple active participants and multiple target participants, their specific role being distinguished in the "type_cd" of the respective instance of the Participation class. In particular, an act involving coordination of care may involve two or more active participants -- playing different roles -- who interact on behalf of a patient, family, or aggregate in the role of target participant. For example, a nurse (active participant) calls Meals on Wheels (active participant) on behalf of the patient (target participant). An act includes the "results", "answers" or informational "procedure products" gained during the act. In this model, "results" do not exist without an act, and every clinical result, including those results gained accidentally, is gleaned via an act. In other moods, such as "definition " or "intent", the results are the possible results, the expected or aimed-for results, or the tested-for results."""; :label "Act"; :subClassOf kb:HL7RIM . a rdf:Property; a:maxCardinality "1"; :comment """A time expression specifying the occasion time or time of happening for the Act. This is the time when the action happened, is ordered or scheduled to happen, or when it can possibly happen (depending on the mood of the Act). When used with procedures and other events, this is the total time of activity including preparation and clean-up actions. Thus it may be longer than the effective time of the same act, which is the period during which the procedure actually takes place."""; :domain kb:Act; :label "Act.activity_time"; :range kb:GTS . a rdf:Property; a:maxCardinality "1"; :comment """A time expression specifying the point in time at which information about Act first became available. For HL7 messaging, the Act.availability_time will be set according to the sender system. The Act.availability_time is an inert attribute with respect to the mood code. This means, it is the recording time of the act object regardless of its mood. Rationale: A database that records a separate time stamp for both valid time and transaction time is called a bi-temporal database. Bi-temporal databases allow reconstructing at any time what users of the database actually could have known, versus what the state of the world was at that time. For example, one might record that a patient had a right-ventricular myocardial infarction effective three hours ago, but we may only know about this unusual condition a few minutes ago. Thus, any interventions from three hours ago until a few minutes ago may have assumed a usual left-ventricular infarction, which can explain why these interventions may not have been appropriate in light of the more recent knowledge about the prior state. However, the transaction time (or recording time) may vary from system to system."""; :domain kb:Act; :label "Act.availability_time"; :range kb:TS . a rdf:Property; a:maxCardinality "1"; a:values , , ; :comment """A code specifying which particular kind of Act that the Act represents within its class. The kind of Act (e.g. physical examination, serum potassium, patient encounter, 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, perhaps SNOMED for procedures, etc."""; :domain kb:Act; :label "Act.cd"; :range kb:CD . a rdf:Property; a:maxCardinality "1"; a:values ; :comment "A code specifying the class or category of Acts that the specific Act represents. The code indicates which class in the Act hierarchy is represented by any instance of Act."; :domain kb:Act; :label "Act.class_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; a:values , , ; :comment """A code specifying limits regarding the disclosure of information about Act. It is important to note that good confidentiality of the medical record cannot be achieved solely through confidentiality codes to mask individual record items from certain types of users. Aggregations of data should assume the privacy level of the most private action in the aggregation."""; :domain kb:Act; :label "Act.confidentiality_cd"; :range . a rdf:Property; a:maxCardinality "1"; :comment "Indicates that all acts connected through context-conductive links should not be independently removed from the context of this act."; :domain kb:Act; :label "Act.context_lock_ind"; :range kb:BL . a rdf:Property; a:maxCardinality "1"; :comment """A time expression specifying the focal or operative time of the Act This is the time at which the action focuses. It is also known as the "primary" time (Arden Syntax) or the "biologically relevant time" (HL7 v2.x). This attribute is distinguished from activity time. For observations, the time of the observation activity may be much later than the time of the observed feature. For instance, in a Blood Gas Analysis (BGA), a result will always come up several minutes after the specimen was taken, meanwhile the patient's physiological state may have changed significantly. For surgical procedures the time between first cut and last suture is taken as the effective time of the procedure. For transport and supply acts the effective time is the time en route or time of delivery respectively (discounting the travel time to the pick-up location and from the drop-off location.) For administrative acts, such as patient encounters, this is the "administrative" time, i.e., the encounter start and end date required to be chosen by business rules, as opposed to the actual time the healthcare encounter related work is performed (which would be the activity_time.) ExtRef: UB92 FL 17, UB91 FL 18"""; :domain kb:Act; :label "Act.effective_time"; :range kb:GTS . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid500"; :domain kb:Act; :label "Act.for"; :range kb:Participation . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid492"; :domain kb:Act; :label "Act.has_source"; :range kb:Act_relationship . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid496"; :domain kb:Act; :label "Act.has_target"; :range kb:Act_relationship . a rdf:Property; a:maxCardinality "1"; :comment "A unique identifier for the Act."; :domain kb:Act; :label "Act.id"; :range . a rdf:Property; a:maxCardinality "1"; :comment """An indicator specifying whether the Act can occur independently of other Acts. Some acts can only be manipulated as subordinate to a composite act. Others are abstractions of acts or inseparable act groups that should only be manipulated together. This attribute is true by default."""; :domain kb:Act; :label "Act.independent_ind"; :range kb:BL . a rdf:Property; a:maxCardinality "1"; :comment "An indicator specifying whether Act is interruptible by other, asynchronous Acts"; :domain kb:Act; :label "Act.interruptible_ind"; :range kb:BL . a rdf:Property; a:maxCardinality "1"; :comment "The language used in documenting the Act."; :domain kb:Act; :label "Act.language_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; a:values , ; :comment """A code specifying whether the Act is an activity that has happened, can happen, is happening, is intended to happen, or is requested/demanded to happen. Webster's dictionary defines mood of a verb as a "distinction of form ... of a verb to express whether the action or state it denotes is conceived as fact or in some other manner (as command, possibility, or wish)". This definition of mood is applied directly activities in health care where the action may be conceived as an event that happened (fact), an ordered act (command), a possible act (master file), or a goal (wish)."""; :domain kb:Act; :label "Act.mood_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment "An indicator specifying that the Act is a negation of the Act event specified by Act.class_cd and Act.cd.\nFor example when used with Act.class_cd \"Observation\" it allows one to say \"patient has no chest pain\". In criterion mood it negates the criterion analogously, e.g., \"if systolic blood pressure is not within 90-100 mmHg then alert me.\""; :domain kb:Act; :label "Act.negation_ind"; :range kb:BL . a rdf:Property; a:maxCardinality "1"; :comment """A code or set of codes specifying the urgency under which the Act happened, can happen, is happening, is intended to happen, or is requested/demanded to happen. This attribute is used in orders to indicate the ordered priority, and in event documentation it indicates the actual priority used to perform the act. In definition mood it indicates the available priorities."""; :domain kb:Act; :label "Act.priority_cd"; :range . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid502"; :domain kb:Act; :label "Act.provides_context_for"; :range kb:Act_context . a rdf:Property; a:maxCardinality "1"; a:values , ; :comment "A code specifying the motivation, cause, or rationale for non-clinical actions represented by Act."; :domain kb:Act; :label "Act.reason_cd"; :range . a rdf:Property; a:maxCardinality "1"; :comment """An interval of integer numbers stating the minimal and maximal number of repetitions of the Act. The number of repeats is additionally constrained by time. The act will repeat at least the minimal number times and at most, the maximal number of times. Repetitions will also terminate when the time exceeds the maximal Act.effective_time, whichever comes first."""; :domain kb:Act; :label "Act.repeat_nbr"; :range . a rdf:Property; a:maxCardinality "1"; a:values , , ; :comment "A code specifying the state of the Act."; :domain kb:Act; :label "Act.status_cd"; :range . a rdf:Property; a:maxCardinality "1"; :comment """A textual or multimedia description of the Act. There is no restriction on length or content imposed on the Act.txt attribute. The content of the description is not considered part of the functional information communicated between systems. Free text descriptions are used to help an individual interpret the content and context of the act. All information relevant for automated functions must be communicated using the proper attributes and associated objects. As with any attribute of the Act class, the meaning of the Act.txt attribute is subject to the Act.mood_cd. For act definitions, the description can contain textbook-like information about that act. For act orders, the description will contain particular instructions pertaining only to that order. Filler order systems must show the description field to a performing provider."""; :domain kb:Act; :label "Act.txt"; :range kb:ED . kb:ActClass a :Class; :label "ActClass"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "ActClass.ACCM"; :subClassOf . a kb:CS; ; :label "ActClass.ACCT"; :subClassOf . a kb:CS; ; :label "ActClass.ALRT"; :subClassOf . a kb:CS; ; :label "ActClass.ARTBLD"; :subClassOf . a kb:CS; ; :label "ActClass.AUTH"; :subClassOf . a kb:CS; ; :label "ActClass.ActClinicalDocument "; :subClassOf . a kb:CS; ; :label "ActClass.ActConfirmationClass"; :subClassOf . a kb:CS; ; :label "ActClass.ActContractClass "; :subClassOf . a kb:CS; ; :label "ActClass.ActDocumentStructureClass"; :subClassOf . a kb:CS; ; :label "ActClass.ActFinancialClass "; :subClassOf . a kb:CS; ; :label "ActClass.ActFinancialContractClass "; :subClassOf . a kb:CS; ; :label "ActClass.ActIncidentClass "; :subClassOf . a kb:CS; ; :label "ActClass.ActInvoiceElementClass "; :subClassOf . a kb:CS; ; :label "ActClass.ActLabObsClass"; :subClassOf . a kb:CS; ; :label "ActClass.ActObservationClass "; :subClassOf . a kb:CS; ; :label "ActClass.ActPublicHealthCaseClass "; :subClassOf . a kb:CS; ; :label "ActClass.ActRootClass"; :subClassOf kb:ActClass . a kb:CS; ; :label "ActClass.ActServiceListClass"; :subClassOf . a kb:CS; ; :label "ActClass.ActServiceListIssuesClass "; :subClassOf . a kb:CS; ; :label "ActClass.ActSupplyClass "; :subClassOf . a kb:CS; ; :label "ActClass.ActWorkingListClass "; :subClassOf . a kb:CS; ; :label "ActClass.CDALVLONE"; :subClassOf . a kb:CS; ; :label "ActClass.CEVN"; :subClassOf . a kb:CS; ; :label "ActClass.CNTM"; :subClassOf . a kb:CS; ; :label "ActClass.CONS"; :subClassOf . a kb:CS; ; :label "ActClass.CONTREG"; :subClassOf . a kb:CS; ; :label "ActClass.COV"; :subClassOf . a kb:CS; ; :label "ActClass.CTXT"; :subClassOf . a kb:CS; ; :label "ActClass.DGIMG"; :subClassOf . a kb:CS; ; :label "ActClass.DIET"; :subClassOf . a kb:CS; ; :label "ActClass.DILUTION"; :subClassOf . a kb:CS; ; :label "ActClass.DOCBODY"; :subClassOf . a kb:CS; ; :label "ActClass.DOCCNTNT"; :subClassOf . a kb:CS; ; :label "ActClass.DOCLSTITM"; :subClassOf . a kb:CS; ; :label "ActClass.DOCPARA"; :subClassOf . a kb:CS; ; :label "ActClass.DOCSECT"; :subClassOf . a kb:CS; ; :label "ActClass.DOCTBL"; :subClassOf . a kb:CS; ; :label "ActClass.DocumentList "; :subClassOf . a kb:CS; ; :label "ActClass.DocumentTableCell"; :subClassOf . a kb:CS; ; :label "ActClass.DocumentTableColumnStructure"; :subClassOf . a kb:CS; ; :label "ActClass.DocumentTableRowGroup"; :subClassOf . a kb:CS; ; :label "ActClass.DocumentTableRowStructure"; :subClassOf . a kb:CS; ; :label "ActClass.DocumentTableStructure"; :subClassOf . a kb:CS; ; :label "ActClass.ELIG"; :subClassOf . a kb:CS; ; :label "ActClass.ENC"; :subClassOf . a kb:CS; ; :label "ActClass.ENVFCTS"; :subClassOf . a kb:CS; ; :label "ActClass.GOL"; :subClassOf . a kb:CS; ; :label "ActClass.INFINVE"; :subClassOf . a kb:CS; ; :label "ActClass.INS"; :subClassOf . a kb:CS; ; :label "ActClass.INTFRIDX"; :subClassOf . a kb:CS; ; :label "ActClass.JOBINC"; :subClassOf . a kb:CS; ; :label "ActClass.LOG"; :subClassOf . a kb:CS; ; :label "ActClass.ListType"; :subClassOf . a kb:CS; ; :label "ActClass.MPROT"; :subClassOf . a kb:CS; ; :label "ActClass.OUTB"; :subClassOf . a kb:CS; ; :label "ActClass.PRB"; :subClassOf . a kb:CS; ; :label "ActClass.PROC"; :subClassOf . a kb:CS; ; :label "ActClass.REFCOORD"; :subClassOf . a kb:CS; ; :label "ActClass.REFR"; :subClassOf . a kb:CS; ; :label "ActClass.REG"; :subClassOf . a kb:CS; ; :label "ActClass.SBADM"; :subClassOf . a kb:CS; ; :label "ActClass.SCH"; :subClassOf . a kb:CS; ; :label "ActClass.SPCTRT"; :subClassOf . a kb:CS; ; :label "ActClass.TBLCOL"; :subClassOf . a kb:CS; ; :label "ActClass.TBLCOLGP"; :subClassOf . a kb:CS; ; :label "ActClass.TBLDATA"; :subClassOf . a kb:CS; ; :label "ActClass.TBLHDR"; :subClassOf . a kb:CS; ; :label "ActClass.TBLROW"; :subClassOf . a kb:CS; ; :label "ActClass.TEMP"; :subClassOf . a kb:CS; ; :label "ActClass.TRNS"; :subClassOf . a kb:CS; ; :label "ActClass.TableRowGroupType"; :subClassOf . a kb:CS; ; :label "ActClass.VOLUME"; :subClassOf . a kb:CS; ; :label "ActClass.XACT"; :subClassOf . a kb:CS; ; :label "ActClass.ordered"; :subClassOf . a kb:CS; ; :label "ActClass.tbody"; :subClassOf . a kb:CS; ; :label "ActClass.tfoot"; :subClassOf . a kb:CS; ; :label "ActClass.thead"; :subClassOf . a kb:CS; ; :label "ActClass.unordered"; :subClassOf . kb:ActCode a :Class; :label "ActCode"; :subClassOf kb:HL7VocabularyConcept . a kb:CD; ; :label "ActCode.02"; :subClassOf . a kb:CD; ; :label "ActCode.03"; :subClassOf . a kb:CD; ; :label "ActCode.04"; :subClassOf . a kb:CD; ; :label "ActCode.06"; :subClassOf . a kb:CD; ; :label "ActCode.07"; :subClassOf . a kb:CD; ; :label "ActCode.09"; :subClassOf . a kb:CD; ; :label "ActCode.10"; :subClassOf . a kb:CD; ; :label "ActCode.11"; :subClassOf . a kb:CD; ; :label "ActCode.12"; :subClassOf . a kb:CD; ; :label "ActCode.13"; :subClassOf . a kb:CD; ; :label "ActCode.15"; :subClassOf . a kb:CD; ; :label "ActCode.16"; :subClassOf . a kb:CD; ; :label "ActCode.17"; :subClassOf . a kb:CD; ; :label "ActCode.A60"; :subClassOf . a kb:CD; ; :label "ActCode.ACID"; :subClassOf . a kb:CD; ; :label "ActCode.ACUTE"; :subClassOf . a kb:CD; ; :label "ActCode.ALK"; :subClassOf . a kb:CD; ; :label "ActCode.AMB"; :subClassOf . a kb:CD; ; :label "ActCode.AN"; :subClassOf . a kb:CD; ; :label "ActCode.ATM"; :subClassOf . a kb:CD; ; :label "ActCode.AUTO-HIGH"; :subClassOf . a kb:CD; ; :label "ActCode.AUTO-LOW"; :subClassOf . a kb:CD; ; :label "ActCode.AVAILABLE"; :subClassOf . a kb:CD; ; :label "ActCode.AccountType"; :subClassOf . a kb:CD; ; :label "ActCode.ActAlertCode"; :subClassOf . a kb:CD; ; :label "ActCode.ActAlertManagementCode"; :subClassOf . a kb:CD; ; :label "ActCode.ActContainerRegistrationCode"; :subClassOf . a kb:CD; ; :label "ActCode.ActDietCode"; :subClassOf . a kb:CD; ; :label "ActCode.ActEncounterCode"; :subClassOf . a kb:CD; ; :label "ActCode.ActIncidentCode"; :subClassOf . a kb:CD; ; :label "ActCode.ActLabObsArtBldCode"; :subClassOf . a kb:CD; ; :label "ActCode.ActLabObsCode"; :subClassOf . a kb:CD; ; :label "ActCode.ActLabObsDilutionCode"; :subClassOf . a kb:CD; ; :label "ActCode.ActLabObsEvnfctsCode"; :subClassOf . a kb:CD; ; :label "ActCode.ActLabObsInterferenceCode"; :subClassOf . a kb:CD; ; :label "ActCode.ActLabObsVolumeCode"; :subClassOf . a kb:CD; ; :label "ActCode.ActMonitoringProtocolCode"; :subClassOf . a kb:CD; ; :label "ActCode.ActPharmacySupplyType"; :subClassOf . a kb:CD; ; :label "ActCode.ActProcedureCode"; :subClassOf . a kb:CD; ; :label "ActCode.ActSpecimenTreatmentCode"; :subClassOf . a kb:CD; ; :label "ActCode.ActSuppliedItemAlertCode"; :subClassOf . a kb:CD; ; :label "ActCode.AdministrationAlertCode"; :subClassOf . a kb:CD; ; :label "ActCode.BR"; :subClassOf . a kb:CD; ; :label "ActCode.CASH"; :subClassOf . a kb:CD; ; :label "ActCode.CHRG"; :subClassOf . a kb:CD; ; :label "ActCode.CIRCLE"; :subClassOf . a kb:CD; ; :label "ActCode.CONSUMPTION"; :subClassOf . a kb:CD; ; :label "ActCode.CURRENT"; :subClassOf . a kb:CD; ; :label "ActCode.ClinicalDrug"; :subClassOf . a kb:CD; ; :label "ActCode.ComplianceAlertCode "; :subClassOf . a kb:CD; ; :label "ActCode.ConsultedPrescriberManagementCode "; :subClassOf . a kb:CD; ; :label "ActCode.ControlledSubstanceMonitoringProtocol "; :subClassOf . a kb:CD; ; :label "ActCode.CreditCard"; :subClassOf . a kb:CD; ; :label "ActCode.DADR"; :subClassOf . a kb:CD; ; :label "ActCode.DAGE"; :subClassOf . a kb:CD; ; :label "ActCode.DALCH"; :subClassOf . a kb:CD; ; :label "ActCode.DALGY"; :subClassOf . a kb:CD; ; :label "ActCode.DDRG"; :subClassOf . a kb:CD; ; :label "ActCode.DEFB"; :subClassOf . a kb:CD; ; :label "ActCode.DF"; :subClassOf . a kb:CD; ; :label "ActCode.DFOOD"; :subClassOf . a kb:CD; ; :label "ActCode.DGEN"; :subClassOf . a kb:CD; ; :label "ActCode.DGEND"; :subClassOf . a kb:CD; ; :label "ActCode.DHERB"; :subClassOf . a kb:CD; ; :label "ActCode.DINT"; :subClassOf . a kb:CD; ; :label "ActCode.DLAB"; :subClassOf . a kb:CD; ; :label "ActCode.DLACT"; :subClassOf . a kb:CD; ; :label "ActCode.DM"; :subClassOf . a kb:CD; ; :label "ActCode.DN"; :subClassOf . a kb:CD; ; :label "ActCode.DOSEDURH"; :subClassOf . a kb:CD; ; :label "ActCode.DOSEDURL"; :subClassOf . a kb:CD; ; :label "ActCode.DOSEH"; :subClassOf . a kb:CD; ; :label "ActCode.DOSEIVL"; :subClassOf . a kb:CD; ; :label "ActCode.DOSEL"; :subClassOf . a kb:CD; ; :label "ActCode.DPREG"; :subClassOf . a kb:CD; ; :label "ActCode.DUPTHPY"; :subClassOf . a kb:CD; ; :label "ActCode.DV"; :subClassOf . a kb:CD; ; :label "ActCode.DocumentSectionType"; :subClassOf . a kb:CD; ; :label "ActCode.DocumentType"; :subClassOf . a kb:CD; ; :label "ActCode.DosageProblemAlertCode "; :subClassOf . a kb:CD; ; :label "ActCode.DoseDurationAlertCode "; :subClassOf . a kb:CD; ; :label "ActCode.DrugAppropriatenessAlertCode"; :subClassOf . a kb:CD; ; :label "ActCode.DrugConditionAlertCode "; :subClassOf . a kb:CD; ; :label "ActCode.DrugInteractionAlertCode"; :subClassOf . a kb:CD; ; :label "ActCode.DrugObservationAlertCode "; :subClassOf . a kb:CD; ; :label "ActCode.DrugReactionAlertCode "; :subClassOf . a kb:CD; ; :label "ActCode.ELLIPSE"; :subClassOf . a kb:CD; ; :label "ActCode.EMER"; :subClassOf . a kb:CD; ; :label "ActCode.EmergencyPharmacySupplyType "; :subClassOf . a kb:CD; ; :label "ActCode.EncounterAccomodation"; :subClassOf . a kb:CD; ; :label "ActCode.ExternallyDefinedActCodes"; :subClassOf kb:ActCode . a kb:CD; ; :label "ActCode.FAST"; :subClassOf . a kb:CD; ; :label "ActCode.FFC"; :subClassOf . a kb:CD; ; :label "ActCode.FFP"; :subClassOf . a kb:CD; ; :label "ActCode.FIBRIN"; :subClassOf . a kb:CD; ; :label "ActCode.FILT"; :subClassOf . a kb:CD; ; :label "ActCode.FLD"; :subClassOf . a kb:CD; ; :label "ActCode.FLUR"; :subClassOf . a kb:CD; ; :label "ActCode.FS"; :subClassOf . a kb:CD; ; :label "ActCode.FinancialTransactionType"; :subClassOf . a kb:CD; ; :label "ActCode.FirstFillPharmacySupplyType "; :subClassOf . a kb:CD; ; :label "ActCode.GF"; :subClassOf . a kb:CD; ; :label "ActCode.HEMOLYSIS"; :subClassOf . a kb:CD; ; :label "ActCode.HH"; :subClassOf . a kb:CD; ; :label "ActCode.HL7DefinedActCodes"; :subClassOf kb:ActCode . a kb:CD; ; :label "ActCode.I"; :subClassOf , . a kb:CD; ; :label "ActCode.ICTERUS"; :subClassOf . a kb:CD; ; :label "ActCode.INITIAL"; :subClassOf . a kb:CD; ; :label "ActCode.L"; :subClassOf . a kb:CD; ; :label "ActCode.LDLP"; :subClassOf . a kb:CD; ; :label "ActCode.LF"; :subClassOf . a kb:CD; ; :label "ActCode.LIPEMIA"; :subClassOf . a kb:CD; ; :label "ActCode.LP"; :subClassOf . a kb:CD; ; :label "ActCode.LQ"; :subClassOf . a kb:CD; ; :label "ActCode.LS"; :subClassOf . a kb:CD; ; :label "ActCode.LogicalObservationIdentifierNamesAndCodes"; :subClassOf . a kb:CD; ; :label "ActCode.M"; :subClassOf . a kb:CD; ; :label "ActCode.MC"; :subClassOf . a kb:CD; ; :label "ActCode.MS"; :subClassOf . a kb:CD; ; :label "ActCode.MVA"; :subClassOf . a kb:CD; ; :label "ActCode.ManufacturedDrug"; :subClassOf . a kb:CD; ; :label "ActCode.N"; :subClassOf . a kb:CD; ; :label "ActCode.NEUT"; :subClassOf . a kb:CD; ; :label "ActCode.NF"; :subClassOf . a kb:CD; ; :label "ActCode.NONAC"; :subClassOf . a kb:CD; ; :label "ActCode.O"; :subClassOf . a kb:CD; ; :label "ActCode.ObservationDiagnosisTypes"; :subClassOf . a kb:CD; ; :label "ActCode.ObservationType"; :subClassOf kb:ActCode . a kb:CD; ; :label "ActCode.OtherActionTakenManagementCode "; :subClassOf . a kb:CD; ; :label "ActCode.P"; :subClassOf , . a kb:CD; ; :label "ActCode.PAF"; :subClassOf . a kb:CD; ; :label "ActCode.PAR"; :subClassOf . a kb:CD; ; :label "ActCode.PLYDOC"; :subClassOf . a kb:CD; ; :label "ActCode.PLYPHRM"; :subClassOf . a kb:CD; ; :label "ActCode.POINT"; :subClassOf . a kb:CD; ; :label "ActCode.POLY"; :subClassOf . a kb:CD; ; :label "ActCode.PRE"; :subClassOf . a kb:CD; ; :label "ActCode.R"; :subClassOf . a kb:CD; ; :label "ActCode.RD"; :subClassOf . a kb:CD; ; :label "ActCode.RDADR"; :subClassOf . a kb:CD; ; :label "ActCode.RDALGY"; :subClassOf . a kb:CD; ; :label "ActCode.RDINT"; :subClassOf . a kb:CD; ; :label "ActCode.RECA"; :subClassOf . a kb:CD; ; :label "ActCode.RERUN"; :subClassOf . a kb:CD; ; :label "ActCode.REV"; :subClassOf . a kb:CD; ; :label "ActCode.RFC"; :subClassOf . a kb:CD; ; :label "ActCode.RFF"; :subClassOf . a kb:CD; ; :label "ActCode.RFP"; :subClassOf . a kb:CD; ; :label "ActCode.ReferencedCoordinateRegionType"; :subClassOf . a kb:CD; ; :label "ActCode.RefillPharmacySupplyType "; :subClassOf . a kb:CD; ; :label "ActCode.RelatedDrugReactionAlertCode "; :subClassOf . a kb:CD; ; :label "ActCode.S"; :subClassOf . a kb:CD; ; :label "ActCode.SCH"; :subClassOf . a kb:CD; ; :label "ActCode.SEV"; :subClassOf . a kb:CD; ; :label "ActCode.SFHB"; :subClassOf . a kb:CD; ; :label "ActCode.SO"; :subClassOf . a kb:CD; ; :label "ActCode.SP"; :subClassOf . a kb:CD; ; :label "ActCode.SubstanceAdministrationActCode"; :subClassOf . a kb:CD; ; :label "ActCode.SupplyAlertCode"; :subClassOf . a kb:CD; ; :label "ActCode.SupplyAppropriateManagementCode "; :subClassOf . a kb:CD; ; :label "ActCode.T"; :subClassOf . a kb:CD; ; :label "ActCode.TB"; :subClassOf . a kb:CD; ; :label "ActCode.TF"; :subClassOf . a kb:CD; ; :label "ActCode.TOOLATE"; :subClassOf . a kb:CD; ; :label "ActCode.TOOSOON"; :subClassOf . a kb:CD; ; :label "ActCode.TherapyAppropriateManagementCode "; :subClassOf . a kb:CD; ; :label "ActCode.UD"; :subClassOf . a kb:CD; ; :label "ActCode.UFIL"; :subClassOf . a kb:CD; ; :label "ActCode.V"; :subClassOf . a kb:CD; ; :label "ActCode.VLI"; :subClassOf . a kb:CD; ; :label "ActCode.VR"; :subClassOf . a kb:CD; ; :label "ActCode.W"; :subClassOf . a kb:CD; ; :label "ActCode.WPA"; :subClassOf . a kb:CD; ; :label "ActCode.X"; :subClassOf . a kb:CS; ; :label "ActDocumentRelationship.XFRM"; :subClassOf . kb:ActMood a :Class; :label "ActMood"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "ActMood.APT"; :subClassOf . a kb:CS; ; :label "ActMood.ARQ"; :subClassOf . a kb:CS; ; :label "ActMood.CompletionTrack"; :subClassOf kb:ActMood . a kb:CS; ; :label "ActMood.DEF"; :subClassOf . a kb:CS; ; :label "ActMood.EVN"; :subClassOf . a kb:CS; ; :label "ActMood.EVN.CRT"; :subClassOf . a kb:CS; ; :label "ActMood.Intent "; :subClassOf . a kb:CS; ; :label "ActMood.OPT"; :subClassOf . a kb:CS; ; :label "ActMood.ORD"; :subClassOf . a kb:CS; ; :label "ActMood.Predicate"; :subClassOf kb:ActMood . a kb:CS; ; :label "ActMood.Proposal "; :subClassOf . a kb:CS; ; :label "ActMood.RMD"; :subClassOf . kb:ActReason a :Class; :label "ActReason"; :subClassOf kb:HL7VocabularyConcept . a ; ; :label "ActReason.BLK"; :subClassOf . a ; ; :label "ActReason.DEC"; :subClassOf . a ; ; :label "ActReason.ER"; :subClassOf . a ; ; :label "ActReason.FIN"; :subClassOf . a ; ; :label "ActReason.MED"; :subClassOf . a ; ; :label "ActReason.MTG"; :subClassOf . a ; ; :label "ActReason.PAT"; :subClassOf . a ; ; :label "ActReason.PHY"; :subClassOf . a ; ; :label "ActReason.RQ"; :subClassOf . a ; ; :label "ActReason.Scheduling"; :subClassOf kb:ActReason . a ; ; :label "ActReason.Transfer"; :subClassOf kb:ActReason . kb:ActRelationship a :Class; :label "ActRelationship"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "ActRelationship.APND"; :subClassOf , . a kb:CS; ; :label "ActRelationship.AUTH"; :subClassOf . a kb:CS; ; :label "ActRelationship.CAUS"; :subClassOf . a kb:CS; ; :label "ActRelationship.CHRG"; :subClassOf . a kb:CS; ; :label "ActRelationship.CIND"; :subClassOf . a kb:CS; ; :label "ActRelationship.COMP"; :subClassOf kb:ActRelationship . a kb:CS; ; :label "ActRelationship.COST"; :subClassOf . a kb:CS; ; :label "ActRelationship.COVBY"; :subClassOf . a kb:CS; ; :label "ActRelationship.CREDIT"; :subClassOf . a kb:CS; ; :label "ActRelationship.DEBIT"; :subClassOf . a kb:CS; ; :label "ActRelationship.DISP"; :subClassOf . a kb:CS; ; :label "ActRelationship.DOC"; :subClassOf kb:ActRelationship . a kb:CS; ; :label "ActRelationship.DRIV"; :subClassOf . a kb:CS; ; :label "ActRelationship.DocumentRelationship"; :subClassOf kb:ActRelationship . a kb:CS; ; :label "ActRelationship.EXPL"; :subClassOf . a kb:CS; ; :label "ActRelationship.Fulfills "; :subClassOf . a kb:CS; ; :label "ActRelationship.GEN"; :subClassOf . a kb:CS; ; :label "ActRelationship.GEVL"; :subClassOf . a kb:CS; ; :label "ActRelationship.GOAL"; :subClassOf . a kb:CS; ; :label "ActRelationship.INST"; :subClassOf . a kb:CS; ; :label "ActRelationship.ITGT"; :subClassOf . a kb:CS; ; :label "ActRelationship.LIMIT"; :subClassOf . a kb:CS; ; :label "ActRelationship.MFST"; :subClassOf . a kb:CS; ; :label "ActRelationship.MTCH"; :subClassOf . a kb:CS; ; :label "ActRelationship.NAME"; :subClassOf . a kb:CS; ; :label "ActRelationship.OBJC"; :subClassOf . a kb:CS; ; :label "ActRelationship.OBJF"; :subClassOf . a kb:CS; ; :label "ActRelationship.OCCR"; :subClassOf . a kb:CS; ; :label "ActRelationship.OPTN"; :subClassOf kb:ActRelationship . a kb:CS; ; :label "ActRelationship.OREF"; :subClassOf . a kb:CS; ; :label "ActRelationship.Outcome "; :subClassOf kb:ActRelationship . a kb:CS; ; :label "ActRelationship.PREV"; :subClassOf . a kb:CS; ; :label "ActRelationship.Pertains "; :subClassOf kb:ActRelationship . a kb:CS; ; :label "ActRelationship.Posts"; :subClassOf kb:ActRelationship . a kb:CS; ; :label "ActRelationship.Precondition "; :subClassOf kb:ActRelationship . a kb:CS; ; :label "ActRelationship.RACT"; :subClassOf . a kb:CS; ; :label "ActRelationship.REFR"; :subClassOf . a kb:CS; ; :label "ActRelationship.REFV"; :subClassOf . a kb:CS; ; :label "ActRelationship.REV"; :subClassOf . a kb:CS; ; :label "ActRelationship.RISK"; :subClassOf . a kb:CS; ; :label "ActRelationship.RSON"; :subClassOf . a kb:CS; ; :label "ActRelationship.Replacement "; :subClassOf kb:ActRelationship, . a kb:CS; ; :label "ActRelationship.Revision "; :subClassOf kb:ActRelationship . a kb:CS; ; :label "ActRelationship.SBST"; :subClassOf . a kb:CS; ; :label "ActRelationship.SCH"; :subClassOf . a kb:CS; ; :label "ActRelationship.SCHE"; :subClassOf . a kb:CS; ; :label "ActRelationship.SPRT"; :subClassOf . a kb:CS; ; :label "ActRelationship.SUCC"; :subClassOf . a kb:CS; ; :label "ActRelationship.SUGG"; :subClassOf . a kb:CS; ; :label "ActRelationship.SUMM"; :subClassOf . a kb:CS; ; :label "ActRelationship.TRIG"; :subClassOf . a kb:CS; ; :label "ActRelationship.UPDT"; :subClassOf . a kb:CS; ; :label "ActRelationship.XFRM"; :subClassOf kb:ActRelationship . kb:ActRelationshipCheckpoint a :Class; :label "ActRelationshipCheckpoint"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "ActRelationshipCheckpoint.B"; :subClassOf kb:ActRelationshipCheckpoint . a kb:CS; ; :label "ActRelationshipCheckpoint.E"; :subClassOf kb:ActRelationshipCheckpoint . a kb:CS; ; :label "ActRelationshipCheckpoint.S"; :subClassOf kb:ActRelationshipCheckpoint . a kb:CS; ; :label "ActRelationshipCheckpoint.T"; :subClassOf kb:ActRelationshipCheckpoint . a kb:CS; ; :label "ActRelationshipCheckpoint.X"; :subClassOf kb:ActRelationshipCheckpoint . kb:ActRelationshipContextControl a :Class; :label "ActRelationshipContextControl"; :subClassOf kb:HL7VocabularyConcept . kb:ActRelationshipJoin a :Class; :label "ActRelationshipJoin"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "ActRelationshipJoin.D"; :subClassOf kb:ActRelationshipJoin . a kb:CS; ; :label "ActRelationshipJoin.K"; :subClassOf kb:ActRelationshipJoin . a kb:CS; ; :label "ActRelationshipJoin.W"; :subClassOf kb:ActRelationshipJoin . a kb:CS; ; :label "ActRelationshipJoin.X"; :subClassOf kb:ActRelationshipJoin . kb:ActRelationshipSplit a :Class; :label "ActRelationshipSplit"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "ActRelationshipSplit.E1"; :subClassOf kb:ActRelationshipSplit . a kb:CS; ; :label "ActRelationshipSplit.EW"; :subClassOf kb:ActRelationshipSplit . a kb:CS; ; :label "ActRelationshipSplit.I1"; :subClassOf kb:ActRelationshipSplit . a kb:CS; ; :label "ActRelationshipSplit.IW"; :subClassOf kb:ActRelationshipSplit . kb:ActSite a :Class; :label "ActSite"; :subClassOf kb:HL7VocabularyConcept . a ; ; :label "ActSite.Animal"; :subClassOf kb:ActSite . a ; ; :label "ActSite.Human"; :subClassOf kb:ActSite . kb:ActStatus a :Class; :label "ActStatus"; :subClassOf kb:HL7VocabularyConcept . a ; ; :label "ActStatus.Normal "; :subClassOf kb:ActStatus . a ; ; :label "ActStatus.aborted"; :subClassOf . a ; ; :label "ActStatus.active"; :subClassOf . a ; ; :label "ActStatus.cancelled"; :subClassOf . a ; ; :label "ActStatus.completed"; :subClassOf . a ; ; :label "ActStatus.held"; :subClassOf . a ; ; :label "ActStatus.new"; :subClassOf . a ; ; :label "ActStatus.nullified"; :subClassOf kb:ActStatus . a ; ; :label "ActStatus.obsolete"; :subClassOf kb:ActStatus . a ; ; :label "ActStatus.suspended"; :subClassOf . kb:Act_context a :Class; :comment """The Act_context is a specialization of an Act that explicitly contains a set of other Acts that share the same context. The "context" of an act is defined as the attribution ascribed to its containing Act_context. OpenIssue: It is recognized as a useful construct but the implication of implied inheritance needs to be resolved. HL7 needs to be cautious about extending the class beyond its original use case. Cardinality on the Act/multiplicity needs to be reviewed (the suggestion is that it needs to be 0 *)."""; :label "Act_context"; :subClassOf kb:Act . a rdf:Property; a:maxCardinality "1"; :comment """The nature or level of the contextual containment that this Act_context provides for the Acts it contains. OpenIssue: The values of this attribute need to be carefully considered to address the open issues relating to inheritance."""; :domain kb:Act_context; :label "Act_context.level_cd"; :range kb:CE . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid505"; :domain kb:Act_context; :label "Act_context.originates_in_context_of"; :range kb:Act . kb:Act_heir a :Class; :comment """Rationale: It has been discovered that one cannot create an HMD choice structure for a set of classes, all of which are sub-types of Act, Role or Entity, but for which there is not a defined physical class. These are the classes that would have been in the RIM as direct descendants (heirs) of Act, Role and Entity, except for the fact that they carried no unique attributes or associations. The addition of this single empty class in each hierarchy will permit messages with the appropriate and necessary choice structures to be built. Subsequent evolution of the methodology and tooling may permit the elimination of these classes in favor of an equivalent abstraction in the methodology."""; :label "Act_heir"; :subClassOf kb:Act . kb:Act_relationship a :Class; :comment """An association between a pair of Acts. This includes Act to Act associations such as collector/component, predecessor/successor, and cause/outcome. The class has two associations to the Act class, one named "source" the other named "target". Consider every Act_relationship instance an arrow with a point (headed to the target) and a butt (coming from the source.) For each relationship type, the functions (or roles) of source and target Act are different. In principle the assignment of functions (roles) to each side of the relationship "arrow" is completely arbitrary. Since the relationships associated with an Act are considered properties of the source act object. That means that the originator of the information reported in an act object is not only responsible for the attribute values of that object, but also for all its outgoing relationships. The rule of attribution is that all act relationships are attributed to the responsible actor of the Act at the source of the Act_relationship (the "source act".) With this recursive act relationship one can group actions into "batteries," e.g., LYTES, CHEM12, or CBC, where multiple routine laboratory tests are ordered as a group. Some groupings, such as CHEM12, appear more arbitrary; others, such as blood pressure, seem to naturally consist of systolic and diastolic pressure. Acts may also be grouped longitudinally, in a sequence of sub-actions to form temporal and conditional (non-temporal) action paths (e.g., care plan, critical path, clinical trials, drug treatment protocols). Acts may be explicitly timed, and may be conditioned on the status or outcome of previous actions. Concurrent collections of acts allow expressing logical branches as well as parallel tasks (tasks carried out at the same time.) These constructs can be organized in multiple layers of nesting, to fully support workflow management. The Act_relationship class is not only used to construct action plans but also to represent clinical reasoning or judgments about action relationships. Prior actions can be linked as the reasons for more recent actions. Supporting evidence can be linked with current clinical hypotheses. Problem lists and other networks of related judgments about clinical events are represented by the Act_relationship link. The Act_relationship.type_cd identifies the meaning and purpose of every Act_relationship instance."""; :label "Act_relationship"; :subClassOf kb:HL7RIM . a rdf:Property; a:maxCardinality "1"; a:values , , , , ; :comment "A code specifying when in the course of an Act a guard condition or pre-condition for the Act is evaluated."; :domain kb:Act_relationship; :label "Act_relationship.checkpoint_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; a:values , , ; :comment "A code specifying the logical conjunction of the criteria in a pair of precondition or outcome Acts."; :domain kb:Act_relationship; :label "Act_relationship.conjunction_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment """A code that specifies if this act relationship is conductive to inherited participations and relationships or if it can itself be inherited. Act relationships and participations that are marked inheritable can be inherited along act-relationships that are marked conductive. Conductance of inheritable objects is transitive and unidirectional from source to target. The total of all inheritable objects along an uninterrupted chain of conductive links leading back from a target act towards the source of act relationships is called the inherited context of that act. All inherited context is lost at an act relationship marked non-conductive. Context inheritance can be additive (I) or overriding (IOS). Additive inheritance adds new objects into the inherited context while overriding inheritance replaces inherited objects of the same or more specific type/class with this inherited object. Example 1: An observation event has a patient participation marked inheritable and has component observation events linked through act relationships that are marked conductive. This means that the patient participation is a patient participation of those component observation events. Example 2: A composite order has a patient participation, an author participation, and a reason relationship to a diagnosis, all marked as inheritable. The order further has several detail orders as components, with the components marked as conductive. The patient, author, and reason of the component orders are the same as for the composite order."""; :domain kb:Act_relationship; :label "Act_relationship.context_control_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment """An indicator specifying that the Act_Relationship.type_cd should be interpreted as if the roles of the source and target Acts were reversed. The inversion indicator is used when the meaning of Act_relationship_type_cd must be reversed. For example, we define a relationship type reason to express the reason for an action as in: a) "A cholecystectomy was performed because of symptomatic cholelithiasis without signs for cholecystitis." (cholecystectomy has-reason cholelithiasis) This statement of rationale is attributed to the responsible performer of the cholecystectomy. Now consider the following statement: b) "The finding of symptomatic gall stones (cholelithiasis) with no signs of acute cholecystitis suggests a cholecystectomy." While sentence a) declares a reason for an action, sentence b) suggests an action. Reason and suggestion links are reciprocal, i.e., if X has-reason Y, then Y suggests X. The second statement would have been made by the originator of the cholelithiasis finding. In the "network" of interrelated acts, we need to make sure that we do not lose proper attribution of statements to originators ("who said what?") Since attribution is so important, we adopt a very simple rule for it: an act relationship is always attributed to the originator of the source Act. No exceptions to this rule are permitted whatsoever. If attribution needs to be different one can invert the relationship type by setting the inversion_ind attribute to "true". If the inversion indicator is "true", source and target act swap their roles; that is, the reason and the suggested action swap their roles, so that cholecystectomy can be the source and cholelithiasis can be the target. Note that the attribution rule is always unchanged; i.e., the act relationship is always attributed to the responsible author of the source act, no matter what the inversion_ind value is."""; :domain kb:Act_relationship; :label "Act_relationship.inversion_ind"; :range kb:BL . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid490"; :domain kb:Act_relationship; :label "Act_relationship.is_source_for"; :range kb:Act . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid494"; :domain kb:Act_relationship; :label "Act_relationship.is_target_for"; :range kb:Act . a rdf:Property; a:maxCardinality "1"; a:values , , , ; :comment """A code specifying how concurrent Acts are resynchronized in a parallel branch construct. This attribute has its principle use in specifying care plans. A kill branch will only be executed if there is at least one active wait (or exclusive wait) branch. If there is no other wait branch active, a kill branch is not started at all (rather than being discontinued shortly after it is started.) A detached branch will be unrelated to all other branches, thus a kill branch will be discontinued no matter whether there are detached branches still running."""; :domain kb:Act_relationship; :label "Act_relationship.join_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment """An indicator used in Act_relationships that are condition or criterion links. The indicator asserts that the meaning of the link is negated. For conditions and criteria links, indicates whether the meaning is negative (condition must not be true.) Normally all conditions are interpreted as affirmative, i.e., the condition must be true. The negation_ind is part of the condition so that the Boolean outcome of the condition XOR-ed with the negation_ind of the condition link must be true. Thus, if the negation_ind is "true", we say the "condition is true", even if the test was negative."""; :domain kb:Act_relationship; :label "Act_relationship.negation_ind"; :range kb:BL . a rdf:Property; a:maxCardinality "1"; :comment """A specification of a quantity of time that should elapse between the clearance for execution of an Act and the actual beginning of execution. Any entering pre-conditions are tested before the slot is entered, so the pause specifies a minimal waiting time before the act is executed after its pre-conditions become true."""; :domain kb:Act_relationship; :label "Act_relationship.pause_qty"; :range kb:PQ . a rdf:Property; a:maxCardinality "1"; :comment """An integer specifying the relative primacy of the Act_Relationship to other Act_Relationships having the same associated source Act. It is used to represent the priority ordering of conditional branches in act execution plans, or priority ranking in pre-condition, outcome or support links, and preferences among options. The ordering may be total in which all priority numbers are unique, or partial if specific priority values repeat."""; :domain kb:Act_relationship; :label "Act_relationship.priority_nbr"; :range kb:INT . a rdf:Property; a:maxCardinality "1"; :comment """An integer specifying the relative order of the Act_Relationship in relation to other Act_Relationships having the same associated source Act. It is used to represent sequences of actions in execution plans. The ordering may be total, if each sequence number in a set is unique, or partial, if specific sequence numbers are repeated."""; :domain kb:Act_relationship; :label "Act_relationship.sequence_nbr"; :range kb:INT . a rdf:Property; a:maxCardinality "1"; a:values , , , ; :comment "A code specifying how branches are selected for execution when an activity plan has a branch."; :domain kb:Act_relationship; :label "Act_relationship.split_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; a:values , , , , , , , , , , ; :comment "A code specifying the meaning and purpose of every Act_relationship instance. Each of its values implies specific constraints to what kinds of Act objects can be related and in which way."; :domain kb:Act_relationship; :label "Act_relationship.type_cd"; :range kb:CS . kb:AddressPartType a :Class; :label "AddressPartType"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "AddressPartType.ADL"; :subClassOf kb:AddressPartType . a kb:CS; ; :label "AddressPartType.CNT"; :subClassOf kb:AddressPartType . a kb:CS; ; :label "AddressPartType.CPA"; :subClassOf kb:AddressPartType . a kb:CS; ; :label "AddressPartType.CTY"; :subClassOf kb:AddressPartType . a kb:CS; ; :label "AddressPartType.DEL"; :subClassOf kb:AddressPartType . a kb:CS; ; :label "AddressPartType.DIR"; :subClassOf kb:AddressPartType . a kb:CS; ; :label "AddressPartType.HNR"; :subClassOf kb:AddressPartType . a kb:CS; ; :label "AddressPartType.POB"; :subClassOf kb:AddressPartType . a kb:CS; ; :label "AddressPartType.SAL"; :subClassOf kb:AddressPartType . a kb:CS; ; :label "AddressPartType.STA"; :subClassOf kb:AddressPartType . a kb:CS; ; :label "AddressPartType.STR"; :subClassOf kb:AddressPartType . a kb:CS; ; :label "AddressPartType.ZIP"; :subClassOf kb:AddressPartType . kb:AddressUse a :Class; :label "AddressUse"; :subClassOf kb:HL7VocabularyConcept . kb:AdministrativeGender a :Class; :label "AdministrativeGender"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "AdministrativeGender.F"; :subClassOf kb:AdministrativeGender . a kb:CE; ; :label "AdministrativeGender.M"; :subClassOf kb:AdministrativeGender . kb:Assigned_entity a :Class; :comment "An agent role in which the agent is an Entity acting in the employ of an organization. The focus is on functional role on behalf of the organization, unlike the Employee role where the focus is on the 'Human Resources' relationship between the employee and the organization."; :label "Assigned_entity"; :subClassOf kb:Role . a rdf:Property; a:maxCardinality "1"; :comment "http://protege.stanford.edu/kb#genid50"; :domain kb:Assigned_entity; :label "Assigned_entity.position_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment "An indication that the healthcare practitioner is a primary care provider."; :domain kb:Assigned_entity; :label "Assigned_entity.primary_care_ind"; :range kb:BL . kb:Attention_line a :Class; :comment "This class allows parameters for a technology specific transport to be represented in the V3 message outer wrapper."; :label "Attention_line"; :subClassOf kb:HL7RIM . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid1047"; :domain kb:Attention_line; :label "Attention_line.can_include"; :range kb:Transmission . a rdf:Property; a:maxCardinality "1"; :comment "A parameter defining word."; :domain kb:Attention_line; :label "Attention_line.key_word_txt"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; :comment "A parameter value."; :domain kb:Attention_line; :label "Attention_line.value"; :range kb:ST . kb:BAG a :Class; a:role "abstract"; :label "BAG"; :subClassOf kb:ANY . a rdf:Property; :domain kb:BAG; :label "BAG.members"; :range kb:UVP . a :Class; :comment "Generic type instance: Set of addresses"; :label "BAG_AD>"; :subClassOf kb:BAG . a :Class; :comment "Generic type instance: Bag of Entity name"; :label "BAG_EN>"; :subClassOf kb:BAG . a :Class; :comment "Generic type instance: Bag of telecomm addresses"; :label "BAG_TEL>"; :subClassOf kb:BAG . kb:BIN a :Class; :comment """All communicated information must ultimately be physically encoded as binary data. Binary data is the most primitive yet the omnipotent encoding of all information. Binary data is a sequence of uninterpreted bits. A bit is identical with a Boolean value. Thus, all binary data is semantically a sequence of Boolean values. The binary data type is protected, it should not be used directly but only inside the encoded data (ED) type described below. ITS Note: the representation of arbitrary binary data is the responsibility of an ITS. How the ITS accomplishes this depends on the underlying Implementation Technology (whether it is character-based or binary) and on the so represented data. Semantically character data is represented as binary data, however, a character-based ITS should not convert character data into arbitrary binary data and then represent binary data in a character encoding. Ultimately even character-based implementation technology will communicate binary data. It follows from the definition of the sequence generic type (LIST) that an "empty" sequence of binary data is not a valid value but counts as a NULL-value. In other words, non-NULL binary data contains at least one bit."""; :label "BIN"; :subClassOf kb:ANY . kb:BL a :Class; :comment """The Boolean type stands for the values of two-valued logic. A Boolean value can be either "true" or "false". With any data value potentially being NULL, the two-valued logic is effectively extended to a three-valued logic."""; :label "BL"; :subClassOf kb:ANY . a rdf:Property; a:defaultValues "false"; a:maxCardinality "1"; a:range "boolean"; :label "BL.value"; :range :Literal . kb:Batch a :Class; :comment """The Batch class is to specify a message which is a collection of HL7 V3 messages. This class is a placeholder for future specification work by the Control/Query TC. OpenIssue: To be resolved when future work completed."""; :label "Batch"; :subClassOf kb:Transmission . a rdf:Property; a:maxCardinality "1"; :comment "This attribute is available to capture comments related to the batch."; :domain kb:Batch; :label "Batch.batch_comment"; :range . a rdf:Property; a:maxCardinality "1"; :comment "The batch total. It is possible that more than a single batch total exists."; :domain kb:Batch; :label "Batch.batch_total_nbr"; :range . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid1055"; :domain kb:Batch; :label "Batch.is_contained_by"; :range kb:Transmission . a rdf:Property; a:maxCardinality "1"; :comment "This attribute is used by the application processing the batch."; :domain kb:Batch; :label "Batch.nm"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; :comment "This attribute indicates the control identifier of the batch when it was originally transmitted."; :domain kb:Batch; :label "Batch.reference_control_id"; :range kb:II . a rdf:Property; a:maxCardinality "1"; :comment "This attribute contains the count of individual transmissions contained within the batch."; :domain kb:Batch; :label "Batch.transmission_qty"; :range kb:INT . kb:CC a :Class; :comment """The following means that CC can only be used for local codes! invariant(CC x) where x.nonNull .and(x.codeSystem.value(2.16.840.1.113883.3).nonEmpty) { x.modifier.nonEmpty; /* actiually: x.modifier.cardinality.equals(1); */ }"""; :label "CC"; :subClassOf kb:CD . kb:CCR a :Class; :comment "??CodeRoleForCont"; :label "CCR"; :subClassOf kb:CR . kb:CD a :Class; :comment "A concept descriptor represents any kind of concept. The CD refers to a concept usually by citing a code defined in a coding system. A given concept may be expressed in multiple terms where each term is a translation or re-encoding of the meaning in another code system. In addition (and different from translations) compositional code systems are supported. In exceptional cases, the concept descriptor may not contain a code but only free text describing that concept. The CD is typically used through one of its restrictions"; :label "CD"; :subClassOf kb:ANY, :Class . a rdf:Property; a:maxCardinality "1"; a:minCardinality "1"; :comment """This is the plain code symbol, e.g., "784.0" is the code symbol of the ICD-9 code "784.0" for headache. The code must be defined in the coding system. A non-exceptional CD value has a non-NULL code citing a valid code from an identified coding system. Conversely, a CD value without the code or with a code not from the cited coding system is an exceptional value (NULL of flavor other)."""; :domain kb:CD; :label "CD.code"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; :comment """This property specifies the code system that defines the code. Code systems shall be referred to by ISO Object Identifiers (OID). The OID allows unambiguous reference to standard HL7 codes, other standard code systems, and local codes. HL7 shall assign an OID to each of its code tables as well as to external standard coding systems that are being used with HL7. Local sites can use their OID to construct a globally unique local coding system identifier. A non-exceptional CD value (i.e. a CD value that has a non-null code property) has a non-NULL code system specifying the system of concepts that defines the code. In other words whenever there is a code there is also a code system.Although every non-NULL CD value has a defined code system, in some circumstances, the external representation of the CD value needs not explicitly mention the code system. For example, when the context mandates one and only one code system to be used specifying the code system explicitly would be redundant. However, in that case the code system property assumes that context-specific default value and is not NULL. An exceptional CD of NULL-flavor "other" indicates that a concept could not be coded in the coding system specified. Thus, for these coding exceptions, the code system that did not contain the appropriate concept must be provided in the code system property. Some code domains are qualified such that they include the portion of any pertinent local coding system that does not simply paraphrase the standard coding system (CWE.) If a CWE qualified field actually contains such a local code, the coding system must specify the local coding system from which the local code was taken. However, for CWE domains the local code is a valid member of the domain, so that local codes in CWE domains constitute neither an error nor an exceptional (NULL/other) value in the sense of this specification."""; :domain kb:CD; :label "CD.codeSystem"; :range kb:OID . a rdf:Property; a:maxCardinality "1"; :comment """This is a common name of the coding system referred to by the codeSystem OID. The code system name is optional and has no function in communication. The purpose of a code system name is to assist an unaided human interpreter of a code value to interpret the code system OID. It is suggested -- though not absolutely required -- that ITS provide for code system name fields in order to annotate the OID for human comprehension. HL7 systems must not functionally rely on the code system name. The code system name can never modify the meaning of the code system OID value and cannot exist without the OID value."""; :domain kb:CD; :label "CD.codeSystemName"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; :comment """This is a version descriptor defined specifically for the given code system. The code system version is cited as a plain character string. HL7 shall specify how these version strings are formed. If HL7 has not specified how version strings are formed for a particular coding system, version designations have no defined meaning for such coding system. For the purpose of this specification, the term "version" means the following: Different versions of one code system must be compatible in general. Whenever a code system changes in an incompatible way, it will constitute a new code system, not simply a different version, regardless of how the vocabulary publisher calls it. For example, the publisher of ICD-9 and ICD-10 calls these code systems, 'revision 9' and 'revision 10' respectively. However, ICD-10 is a complete redesign of the ICD code, not a backward compatible version. Therefore, for the purpose of this data type specification, ICD-9 and ICD-10 are different code systems, not just different versions. By contrast, when LOINC updates from revision "1.0j" to "1.0k", HL7 would consider this to be just another version of LOINC, since LOINC revisions are backwards compatible."""; :domain kb:CD; :label "CD.codeSystemVersion"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; :comment """The display name is a name or title for the code, under which the sending system typically or actually shows the code value to its users. It is included both as a courtesy to an unaided human interpreter of a code value and as a documentation of the name used to display the concept to the user. The display name has no functional meaning; it can never exist without a code; and it can never modify the meaning of the code. Note: display names may not alter the meaning of the code value. Therefore, display names should not be presented to the user on a receiving application system without ascertaining that the display name adequately represents the concept referred to by the code value. Communication must not simply rely on the display name. The display name�s main purpose is to support debugging of HL7 protocol data units (e.g., messages.)"""; :domain kb:CD; :label "CD.displayName"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; :comment """A concept descriptor may have modifiers if the code system defines such modifiers. Modifiers can only be used with code systems that define rules of postcoordination, where multiple codes together make up one concept. A concept descriptor with modifiers is called a code phrase. For example, SNOMED allows constructing concepts as a combination of multiple codes and HCFA procedure codes come with modifiers. Say, SNOMED RT defines a concept 'leg', a role relation 'has-laterality', and another concept 'left', the concept role relation allows to add the modifier "has-laterality: left" to a primary code "leg" to construct the meaning "left leg". In this example "has-laterality: left" is an element in the modifier. The order of modifiers is preserved, particularly for the case where the coding system allows postcoordination but defines no role names (e.g., some ICD-9 codes, SNOMED, HCFA procedure codes.) Since all the modifier names and subordinate codes of a code phrase should come from the same coding system, a code phrase's coding system should be made the default for all subordinated modifier names and values."""; :domain kb:CD; :label "CD.modifier"; :range . a rdf:Property; a:maxCardinality "1"; :comment """This is the text or phrase used as the basis for the coding. The original text exists in a scenario where an originator of the information does not assign a code, but where the code is assigned later by a coder (post-coding.) In the production of a concept descriptor, original text may thus exist without a code. Although the concept descriptor�s value property is NULL, original text may still exist for the CD value. Any CD value with the code property of NULL signifies a coding exception. In this case, the text property is a name or description of the concept that was not coded. Such exceptional CD may contain translations. Such translations directly encode the concept described in the original text property. Neither display name nor original text is part of the information a receiving system must recognize. An information producer is responsible for the proper coding of all information in the value attribute, for any information consumer may safely ignore the display name and original text attributes. A concept descriptor can be converted into an ED value representing only the original text of the CD value."""; :domain kb:CD; :label "CD.originalText"; :range kb:ED . a rdf:Property; a:maxCardinality "1"; :comment """The translation property of a concept descriptor y holds a set X of other concept descriptors x in X that translate the concept descriptor y into different code systems. Each element x in X was translated from the concept descriptor y. Each translation x may also contain translations. Thus, when a code is translated multiple times the information about which code served as the input to which translation will be preserved. Note: the translations are quasi-synonyms of one real-world concept. Every translation in the set is supposed to express the same meaning 'in other words.' However, exact synonymy does rarely exist between two structurally different coding systems. For this reason, not all of the translations will be equally exact."""; :domain kb:CD; :label "CD.translation"; :range . kb:CE a :Class; :comment """The data type "Coded with Equivalents" (CE) is a restriction of the concept descriptor (CD). The CE suppresses the CD modifier property, which is not applicable. The CE also restricts the translation property such that the translation is a set of CV values. CV values may not themselves contain translations. The CE type is used when the use case indicates that alternative codes may exist and where it is useful to communicate these. The CE type provides for a primary code value, plus a set of alternative or equivalent representations."""; :label "CE"; :subClassOf kb:CD . kb:CR a :Class; :comment """The concept role is used to send code modifiers with optionally named roles. Both modifier roles and values must be defined by the coding system. For example, if SNOMED RT defines a concept "leg", a role relation "has-laterality", and another concept "left", the concept role relation allows to add the modifier "has-laterality: left" to a primary code "leg" to construct the meaning "left leg". The use of modifiers is strictly governed by the code system used. The CD does not permit using code modifiers with code systems that do not provide for modifiers (e.g. pre-coordinated systems, such as LOINC, ICD-10 PCS.) The rules of the modifier use must be governed by the code system (e.g., recent SNOMED RT revision, GALEN.)"""; :label "CR"; :subClassOf kb:ANY . a rdf:Property; a:maxCardinality "1"; :comment """This property indicates if the meaning of the role is inverted. This can be used in cases where the underlying code system defines inversion but does not provide reciprocal pairs of role names. For example, a code system may define the role relation "causes" besides the concepts "Streptococcus pneumoniae" and "Pneumonia". If that code system allows its roles to be inverted, one can construct the post-coordinated concept "Pneumococcus pneumonia" through "Pneumonia -- causes, inverted -- Streptococcus pneumoniae." Roles may only be inverted if the underlying coding systems allows such inversion. Notably, if a coding system defines roles in inverse pairs or intentionally does not define certain inversions, the appropriate role code (e.g. "caused-by") must be used rather than inversion.The property "inverted" should be conveyed in an indicator attribute, whose default value is false. That way the inverted indicator does not have to be sent when the role is not inverted."""; :domain kb:CR; :label "CR.inverted"; :range kb:BL . a rdf:Property; a:maxCardinality "1"; :comment """This is the role name. The role name specifies the manner in which the value contributes to the meaning of a code phrase. For example, if SNOMED RT defines a concept "leg", a role relation "has-laterality", and another concept "left", the concept role relation allows to add the modifier "has-laterality: left" to a primary code "leg" to construct the meaning "left leg". In this example "has-laterality" is the CR.name. If a coding system allows postcoordination but no role names the name attribute can be NULL. The name attribute must be of type CV for which CD must not be substituted."""; :domain kb:CR; :label "CR.name"; :range kb:CV . a rdf:Property; a:maxCardinality "1"; :comment """The code related to the primary code of a code phrase through the role relation. For example, if SNOMED RT defines a concept "leg", a role relation "has-laterality", and another concept "left", the concept role relation allows to add the modifier "has-laterality: left" to a primary code "leg" to construct the meaning "left leg". In this example "left" is the CR.value. This component is of type concept descriptor and thus can be in turn have modifiers. This allows modifiers to nest. Modifiers can only be used as far as the underlying code system defines them. It is not allowed to use any kind of modifiers for code systems that do not explicitly allow and regulate such use of modifiers."""; :domain kb:CR; :label "CR.value"; :range kb:CD . kb:CS a :Class; :comment """The Coded Simple Value (CS) is a restriction of the concept descriptor (CD). The CS suppresses all properties of the CD, except for code and display name. The code system and code system version is fixed by the context in whichy the CS value occurs. Original text is not applicable to CS values. CS can only be used for a coded attribute which has a single HL7-defined value set, and where code additions to that value set require formal HL7 action (such as harmonization.) For these examples, the designation of the domain qualifier will always be CNE and the context determines unambiguously which HL7 value set applies. Such coded attributes that are designated "structural" codes must be assigned the CS restriction."""; :label "CS"; :subClassOf kb:CD . kb:CV a :Class; :comment """The Coded Value (CV) is a restriction of the concept descriptor (CD). The CV suppresses the CD properties translation and modifier, which are both not applicable. The CV also constrains the original text to a character string (ST) instead of the more general encapsulated data (ED) type. This type is used when any reasonable use case will require only a single code value to be sent. Thus, it should not be used in circumstances where multiple alternative codes for a given value are desired. This type may be used with both the CNE and the CWE domain qualifier."""; :label "CV"; :subClassOf kb:CD . kb:CalendarCycle a :Class; :label "CalendarCycle"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "CalendarCycle.OneLetter"; :subClassOf kb:CalendarCycle . a kb:CS; ; :label "CalendarCycle.TwoLetter"; :subClassOf kb:CalendarCycle . kb:Certified_entity a :Class; :comment "A relationship in which the scoper certifies the players ability to perform a specific task. The certification may imply legal capacity, or an evaluated capability for the performance of that task. Examples include the certification of equipment, as well as the granting of license or certificates to organizations or professionals."; :label "Certified_entity"; :subClassOf kb:Role . a rdf:Property; a:maxCardinality "1"; :comment "The date recertification is required."; :domain kb:Certified_entity; :label "Certified_entity.recertification_time"; :range kb:TS . kb:Charset a :Class; :label "Charset"; :subClassOf kb:HL7VocabularyConcept . kb:Clinical_document a :Class; :comment "Specialization of Act to add the characteristics unique to document management services."; :label "Clinical_document"; :subClassOf kb:Context_structure . a rdf:Property; a:maxCardinality "1"; a:values , , , , , , ; :comment "A code depicting the completion status of a report (e.g., incomplete, authenticated, legally authenticated)."; :domain kb:Clinical_document; :label "Clinical_document.completion_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment "Time a document is released (i.e., copied or sent to a display device) from a document management system that maintains revision control over the document. Once valued, cannot be changed. Intent of this attribute is to give the viewer of the document some notion as to how long the document has been out of the safe context of its document management system."; :domain kb:Clinical_document; :label "Clinical_document.copy_time"; :range kb:TS . a rdf:Property; a:maxCardinality "1"; :comment """A report identifier that remains constant across all document revisions that derive from a common original document. An original report is the first version of a report. It gets a new unique value for document_service.set_id, and has the value of document_service.version_nbr set to equal "1". An addendum is an appendage to an existing report that contains supplemental information The appendage is itself an original report. The parent report being appended is referenced via an act_relationsip, with act_relationship.type_cd set to equal "APND" (for "appends"). The parent report being appended remains in place and its content and status are unaltered. A replacemnt report replaces an existing report. The replacement report uses the same value for document_service.set_id as the parent report being replaced, and increments the value of document_serivce.version_nbr by 1. The state of the parent report being replaced should become "superceded" explicitly by another message, but is still retained in the system for historical reference."""; :domain kb:Clinical_document; :label "Clinical_document.set_id"; :range kb:II . a rdf:Property; a:maxCardinality "1"; a:values , , ; :comment "A code depicting the storage status (e.g., active, archived, purged) of a report."; :domain kb:Clinical_document; :label "Clinical_document.storage_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment "Version number is an integer starting at '1' and incrementing by 1. The first instance or original report should always be valued as '1'. The version number value must be incremented by one when a report is replaced, but can also be incremented more often to meet local requirements."; :domain kb:Clinical_document; :label "Clinical_document.version_nbr"; :range kb:INT . kb:CodeSystem a :Class; :label "CodeSystem"; :subClassOf kb:HL7VocabularyConcept . kb:CommunicationFunctionType a :Class; :label "CommunicationFunctionType"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "CommunicationFunctionType.RCV"; :subClassOf kb:CommunicationFunctionType . a kb:CS; ; :label "CommunicationFunctionType.RSP"; :subClassOf kb:CommunicationFunctionType . a kb:CS; ; :label "CommunicationFunctionType.SND"; :subClassOf kb:CommunicationFunctionType . kb:Communication_function a :Class; :comment "Relationship class binds the various entities which function in the transmission (sender, receiver, respond-to) to be linked to the transmission."; :label "Communication_function"; :subClassOf kb:HL7RIM . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid1061"; :domain kb:Communication_function; :label "Communication_function.executed_by"; :range kb:Transmission . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid278"; :domain kb:Communication_function; :label "Communication_function.serves"; :range kb:Entity . a rdf:Property; a:maxCardinality "1"; :comment "The telecomm address that can be used to reach the entity that is serving this function."; :domain kb:Communication_function; :label "Communication_function.telecom"; :range kb:TEL . a rdf:Property; a:maxCardinality "1"; a:values , , ; :comment "The type of communication function being served by the entity with respect to the transmission, such as sender, receiver, respond-to party, etc."; :domain kb:Communication_function; :label "Communication_function.type_cd"; :range kb:CS . kb:CompressionAlgorithm a :Class; :label "CompressionAlgorithm"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "CompressionAlgorithm.DF"; :subClassOf kb:CompressionAlgorithm . a kb:CS; ; :label "CompressionAlgorithm.GZ"; :subClassOf kb:CompressionAlgorithm . a kb:CS; ; :label "CompressionAlgorithm.Z"; :subClassOf kb:CompressionAlgorithm . a kb:CS; ; :label "CompressionAlgorithm.ZL"; :subClassOf kb:CompressionAlgorithm . kb:ConceptGenerality a :Class; :label "ConceptGenerality"; :subClassOf kb:HL7VocabularyConcept . kb:Confidentiality a :Class; :label "Confidentiality"; :subClassOf kb:HL7VocabularyConcept . a ; ; :label "Confidentiality.B"; :subClassOf . a ; ; :label "Confidentiality.ByAccessKind"; :subClassOf kb:Confidentiality . a ; ; :label "Confidentiality.ByInfoType"; :subClassOf kb:Confidentiality . a ; ; :label "Confidentiality.C"; :subClassOf . a ; ; :label "Confidentiality.D"; :subClassOf . a ; ; :label "Confidentiality.ETH"; :subClassOf . a ; ; :label "Confidentiality.I"; :subClassOf . a ; ; :label "Confidentiality.L"; :subClassOf . a ; ; :label "Confidentiality.Modifiers"; :subClassOf kb:Confidentiality . a ; ; :label "Confidentiality.N"; :subClassOf . a ; ; :label "Confidentiality.PSY"; :subClassOf . a ; ; :label "Confidentiality.R"; :subClassOf . a ; ; :label "Confidentiality.S"; :subClassOf . a ; ; :label "Confidentiality.SDV"; :subClassOf . a ; ; :label "Confidentiality.SIV"; :subClassOf . a ; ; :label "Confidentiality.T"; :subClassOf . a ; ; :label "Confidentiality.V"; :subClassOf . kb:Container a :Class; :comment """A container is a manufactured material used to hold other things for purposes such as transportation or protection of contents from loss or damage. With amorphic substances (liquids, gases) a container is required. However, the content of a container is always distinguishable and relatively easily separable from the container, unlike the content (ingredient) of a mixture. A container is related to a content material through Role_relationship.type_cd = "has content". Rationale: The specifications for this class arose from the collaboration between HL7 and the NCCLS. Many of the attribute definitions are drawn from or reference the NCCLS standard."""; :label "Container"; :subClassOf kb:Manufactured_material . a rdf:Property; a:maxCardinality "1"; :comment "The distance from the Point of Reference to the separator material (barrier) within the container. This distance may be provided by the LAS to the instrument and/or specimen processing/handling device to facilitate the insertion of a sampling probe into the specimen without touching the separator. See the Point of Reference definition or in NCCLS standard AUTO5 Laboratory Automation: Electromechanical Interfaces."; :domain kb:Container; :label "Container.barrier_delta_qty"; :range kb:PQ . a rdf:Property; a:maxCardinality "1"; :comment "The distance from the Point of Reference to the outside bottom of the container in units specified below. Refer to Point of Reference definition in section Glossary or in NCCLS standard AUTO5 Laboratory Automation: Electromechanical Interfaces."; :domain kb:Container; :label "Container.bottom_delta_qty"; :range kb:PQ . a rdf:Property; a:maxCardinality "1"; a:values , , , , ; :comment "The type of cap that is to be used with the container for decapping, piercing or other mechanisms."; :domain kb:Container; :label "Container.cap_type_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment "The capacity of the container in the units specified."; :domain kb:Container; :label "Container.capacity_qty"; :range kb:PQ . a rdf:Property; a:maxCardinality "1"; :comment "The outside diameter of the container in units specified."; :domain kb:Container; :label "Container.diameter_qty"; :range kb:PQ . a rdf:Property; a:maxCardinality "1"; :comment "The height of the container in units specified."; :domain kb:Container; :label "Container.height_qty"; :range kb:PQ . a rdf:Property; a:maxCardinality "1"; a:values , ; :comment """A material such as a gel that is contained in blood collection tubes to facilitate separation of blood cells from blood serum by creating a physical "barrier" between them."""; :domain kb:Container; :label "Container.separator_type_cd"; :range kb:CE . kb:ContainerCap a :Class; :label "ContainerCap"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "ContainerCap.CHILD"; :subClassOf . a kb:CE; ; :label "ContainerCap.EASY"; :subClassOf . a kb:CE; ; :label "ContainerCap.FILM"; :subClassOf kb:ContainerCap . a kb:CE; ; :label "ContainerCap.FOIL"; :subClassOf kb:ContainerCap . a kb:CE; ; :label "ContainerCap.MedicationCap"; :subClassOf kb:ContainerCap . a kb:CE; ; :label "ContainerCap.PUSH"; :subClassOf kb:ContainerCap . a kb:CE; ; :label "ContainerCap.SCR"; :subClassOf kb:ContainerCap . kb:ContainerSeparator a :Class; :label "ContainerSeparator"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "ContainerSeparator.GEL"; :subClassOf kb:ContainerSeparator . a kb:CE; ; :label "ContainerSeparator.NONE"; :subClassOf kb:ContainerSeparator . kb:Context_structure a :Class; :comment "A structure is a container within a document. Structures have captions which can be coded. Structures can nest, and structures can contain entries."; :label "Context_structure"; :subClassOf kb:Act . a rdf:Property; a:maxCardinality "1"; :comment "An optional identifier which must be unique within the document."; :domain kb:Context_structure; :label "Context_structure.local_id"; :range kb:ST . kb:Control_event a :Class; :comment """The Event is the focal point of information assembled in response to the occurrence of a "controlled event." "Participations" and "Acts" related to a "controlled event" ard assembled in a package with the RIM content that a domain technical committee specifies as the main payload of information to be communicated to document the event. This package can be placed in a message envelope, directed to an application managing documents or any application with component interfaces to this package of structured information content. OpenIssue: Look at the symmetry between how messages and documents are structured. This is work that is yet to be completed."""; :label "Control_event"; :subClassOf kb:Act . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid1019"; :domain kb:Control_event; :label "Control_event.has_payload"; :range kb:Message . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid1053"; :domain kb:Control_event; :label "Control_event.occurs_with"; :range kb:Query_event . a rdf:Property; a:maxCardinality "1"; a:values , , , , , , ; :comment "Specifies whether a response is expected from the addressee of this interaction and what level of detail that response should include."; :domain kb:Control_event; :label "Control_event.response_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment "Attribute identifying the structure of the payload portion of the message specified for this interaction."; :domain kb:Control_event; :label "Control_event.structure_type_id"; :range kb:II . kb:CoverageSource a :Class; :label "CoverageSource"; :subClassOf kb:HL7VocabularyConcept . kb:CS a :Class. kb:DataType a :Class; :label "DataType"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "DataType.DataValue"; :subClassOf kb:DataType . kb:Determiner a :Class; :label "Determiner"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "Determiner.Determined"; :subClassOf kb:Determiner . a kb:CS; ; :label "Determiner.INSTANCE"; :subClassOf kb:Determiner . a kb:CS; ; :label "Determiner.QUANTIFIED_KIND"; :subClassOf . kb:Device a :Class; :comment "A device is anything used in an activity without being substantially changed through that activity. This includes durable (reusable) medical equipment as well as disposable equipment. The kind of device is identified by the Entity.cd."; :label "Device"; :subClassOf kb:Manufactured_material . a rdf:Property; a:maxCardinality "1"; a:values , , , ; :comment "This field identifies the current functional activity of the automated device. The value of alert_level_cd is determined by the machine itself."; :domain kb:Device; :label "Device.alert_level_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment """Date of last calibration and/or inspection of the device. OpenIssue: Is this linked somehow with the �maintainer�? OpenIssue: Given the definition of the class, this attribute would be moved up to Manufactured_material."""; :domain kb:Device; :label "Device.last_calibration_time"; :range kb:TS . a rdf:Property; a:maxCardinality "1"; a:values , ; :comment """The current state of control associated with the equipment. An equipment can either work autonomously (local_remote_control_state_cd="Local") or it can be controlled by another system (local_remote_control_state_cd="Remote")."""; :domain kb:Device; :label "Device.local_remote_control_state_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment "Name of the version of this device as designated by the manufacturer."; :domain kb:Device; :label "Device.manufacturer_model_nm"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; :comment "Name, version and release of the software that operates the device."; :domain kb:Device; :label "Device.software_nm"; :range kb:ST . kb:DeviceAlertLevel a :Class; :label "DeviceAlertLevel"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "DeviceAlertLevel.C"; :subClassOf kb:DeviceAlertLevel . a kb:CE; ; :label "DeviceAlertLevel.N"; :subClassOf kb:DeviceAlertLevel . a kb:CE; ; :label "DeviceAlertLevel.S"; :subClassOf kb:DeviceAlertLevel . a kb:CE; ; :label "DeviceAlertLevel.W"; :subClassOf kb:DeviceAlertLevel . kb:Device_task a :Class; :comment "An activity of an automated system. Such activities are invoked either by an outside command or are scheduled and executed spontaneously by the device (e.g., regular calibration or flushing.) The command to execute the task has mood_cd <= ORD; an executed task (including a task in progress) has mood_cd <= EVN, an automatic task on the schedule has mood_cd <= INT."; :label "Device_task"; :subClassOf kb:Act . a rdf:Property; a:maxCardinality "1"; :comment """The parameters of the task submitted to the device upon issuing of a command (or configuring the schedule of spontaneously executed tasks.) Parameters are only specified here if they are not included in separate HL7 defined structure. The parameters are a list of any data values interpreted by the device. The parameters should be typed with an appropriate HL7 data type (e.g., codes for nominal settings, such as flags, REAL and INT for numbers, TS for points in time, PQ for dimensioned quantities, etc.) However, besides this HL7 data typing, the functioning of the parameters is opaque to the HL7 standardization. Rationale: Some parameters for tasks are uniquely defined by a specific model of equipment. Most critical arguments of a task (e.g., container to operate on, positioning, timing, etc.) are specified in an HL7 standardized structure, and the parameter list would not be used for those. The parameter list is used only for those parameters that cannot be standardized because they are uniquely defined for a specific model of equipment."""; :domain kb:Device_task; :label "Device_task.parameter_value"; :range . kb:Diagnostic_image a :Class; :comment "Class for holding attributes unique to diagnostic images."; :label "Diagnostic_image"; :subClassOf kb:Observation . a rdf:Property; a:maxCardinality "1"; :comment "Patient direction of the rows and columns of the image."; :domain kb:Diagnostic_image; :label "Diagnostic_image.subject_orientation_cd"; :range kb:CE . kb:Diet a :Class; :comment """Diet acts are supply acts, with some aspects resembling Substance_administration acts: the detail of the diet is given as a description of the Material associated via Participation.type_cd="product". Medically relevant diet types may be communicated in the Entity.cd, however, the detail of the food supplied and the various combinations of dishes should be communicated as Material instances."""; :label "Diet"; :subClassOf kb:Supply . a rdf:Property; a:maxCardinality "1"; :comment """For diabetes diet one typically restricts the amount of metabolized carbohydrates to a certain amount per day (e.g., 240 g/d). This restriction can be communicated in the carbohydrate_qty. OpenIssue: Unclear whether the same should not be expressed as associated observations in goal mood (observation.type_cd = carbohydrate intake.)"""; :domain kb:Diet; :label "Diet.carbohydrate_qty"; :range kb:PQ . a rdf:Property; a:maxCardinality "1"; :comment """This value indicates the supplied biologic energy (Calories) per day. This physical quantity should be convertible to 1 kcal/d (or 1 kJ/d.) Note, that there is a lot of confusion about what is a "calorie." There is a "large Calorie" and a "small calorie." On "nutrition facts" labels, the large "Calories" is used. More appropriately, however, one should use the small calorie, which is 1/1000 of a large Calorie. In the Unified Code for Units of Measure, the proper unit symbol for the large calorie is "[Cal]" and for the small calorie it is "cal", or, more commonly used as a kilo-calorie "kcal"."""; :domain kb:Diet; :label "Diet.energy_qty"; :range kb:PQ . kb:DocumentCompletion a :Class; :label "DocumentCompletion"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "DocumentCompletion.AU"; :subClassOf kb:DocumentCompletion . a kb:CE; ; :label "DocumentCompletion.DI"; :subClassOf kb:DocumentCompletion . a kb:CE; ; :label "DocumentCompletion.DO"; :subClassOf kb:DocumentCompletion . a kb:CE; ; :label "DocumentCompletion.IN"; :subClassOf kb:DocumentCompletion . a kb:CE; ; :label "DocumentCompletion.IP"; :subClassOf kb:DocumentCompletion . a kb:CE; ; :label "DocumentCompletion.LA"; :subClassOf kb:DocumentCompletion . a kb:CE; ; :label "DocumentCompletion.PA"; :subClassOf kb:DocumentCompletion . kb:DocumentStorage a :Class; :label "DocumentStorage"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "DocumentStorage.AA"; :subClassOf . a kb:CE; ; :label "DocumentStorage.AR"; :subClassOf kb:DocumentStorage . a kb:CE; ; :label "DocumentStorage.Active "; :subClassOf kb:DocumentStorage . a kb:CE; ; :label "DocumentStorage.PU"; :subClassOf kb:DocumentStorage . kb:ED a :Class; :comment """The encoded data type can convey any data. However, in order for that data to convey meaning, encoded data must be decoded and further interpreted. Encoded data may be a plain character string, formatted text, or any of several kinds of multimedia data. The kind of encoding is conveyed in three properties: 1. type - specifies the protocol, or application used to decode and interpret the data (also known as the "media type" as referring to multi-media data.) 2. charset - identifies the character set and character encoding for character-based "media." 3. compression - data may be given in a compressed form in which case compression identifies the compression algorithm used. Encoded data can be present in two forms, inline or by reference. Inline data is communicated or moved as part of the encoded data value, whereas by-reference data may reside at a different (remote) location. The data is the same whether it is located inline or remote."""; :label "ED"; :subClassOf kb:BIN . a rdf:Property; a:maxCardinality "1"; :comment """For character-based encoding types, this property specifies the character set and character encoding used. The charset is defined according to Internet RFC 2278, IANA Charset Registration Procedures, [http://www.isi.edu/in-notes/rfc2278.txt]. The charset domain is maintained by the Internet Assigned Numbers Authority (IANA) [http://www.isi.edu/in-notes/iana/assignments/character-sets]. The IANA source specifies names and multiple aliases for most character sets. For the HL7's purposes, use of multiple alias names is not allowed. The standard name for HL7 is the one marked by IANA as "preferred for MIME." If IANA has not marked one of the aliases as "preferred for MIME" the main name shall be the one used for HL7. OpenIssue: There are at least 10 different MIME designators for Japanese charsets some being singular character sets (e.g., JIS X208, X212, etc.) or various versions thereof, some being suites of character sets and a switching encoding (e.g., ISO2022, EUC-JP, Shift-JIS, etc.) Allowing that many charsets and versions for Japanese HL7 would be a disservice to the goal for HL7 interoperability. It is unclear what charsets besides JIS X221 (ISO 10646) is needed at all. HL7 Japan is asked to submit two or three (maximum) IETF/MIME registered charsets along with their preferred IETF registered charset code and a description for inclusion into this standard."""; :domain kb:ED; :label "ED.charset"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; a:values , , ; :comment """The compression code indicates whether the raw byte data is compressed, and what compression algorithm was used. Compression may not be allowed for encoded data depending on the attribute or component that is declared encoded data. Character strings (see Section 4.3) may never be compressed."""; :domain kb:ED; :label "ED.compression"; :range kb:CS . a rdf:Property; a:allowedClasses kb:BIN, kb:CS; a:maxCardinality "1"; :comment """The integrity check is a short binary value representing a cryptographically strong checksum that is calculated over the binary data. The purpose of this property, when communicated with a reference is for anyone to validate later whether the reference still resolved to the same data that the reference resolved to when the encoded data value with reference was created. The integrity check is calculated according to the integrity check algorithm. By default, the Secure Hash Algorithm-1 (SHA-1) shall be used. The integrity check is binary encoded according to the rules of the integrity check algorithm. The integrity check is calculated over the raw binary data that is contained in the data component, or that is accessible through the reference. No transformations are made before the integrity check is calculated. If the data is compressed, the Integrity Check is calculated over the compressed data."""; :domain kb:ED; :label "ED.integrityCheck"; :range kb:ANY . a rdf:Property; a:maxCardinality "1"; :comment """This property defines the algorithm used to compute the value in integrity check. The cryptographically strong checksum algorithm Secure Hash Algorithm-1 (SHA-1) [FIPS PUB 180-1: Secure Hash Standard. As of April 17, 1995.] is currently the industry standard. It has superseded the MD5 algorithm only a couple of years ago, when certain flaws in the security of MD5 were discovered. Currently the SHA-1 hash algorithm is the default and mandatory only choice for the integrity check algorithm. However, there is no assurance that SHA-1 will not be superseded at anytime when its flaws will be discovered."""; :domain kb:ED; :label "ED.integrityCheckAlgorithm"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment """For character based information the language property specifies the language of the text. The principles of the code domain of this attribute is specified by RFC 1766, Tags for the Identification of Languages [http://www.isi.edu/in-notes/rfc1766.txt]. It is a set of pre-coordinated pairs of one 2-letter ISO 639 language code and one 2-letter ISO 3166 country code. Language tags do not modify the meaning of the characters found in the text; they are only an advice on if and how to present or communicate the text.For this reason, any system or site that does not deal with multilingual text or names in the real world can safely ignore the language property. representation of language tags to text is highly dependent on the ITS. An ITS should use the native way of language tagging provided by its target implementation technology. Some may have language information in a separate component, e.g., XML has the xml:lang tag for stings. Others may rely on language tags as part of the binary character string representation, e.g., ISO 10646 (Unicode) and its �plane-14� language tags. The language tag should not be mandatory if it is not mandatory in the implementation technology. Semantically, language tagging of strings follows a default-logic. If nothing else is specified the local language is assumed. If a language is set for an entire message or document, that language is the default. If any information element or value that is superior in the syntax hierarchy specifies a language, that language is the default for all subordinate text values. If language tags are present in the beginning of the encoded binary text (e.g., through Unicode�s plane-14 tags) this is the source of the language property of the Encoded Data value. Rationale: The need for a language code for text data values is documented in RFC 2277, IETF Policy on Character Sets and Languages [http://www.isi.edu/in-notes/rfc2277.txt]. Further background information can be found in Using International Characters in Internet Mail [http://www.imc.org/mail-i18n.html], a memo by the Internet Mail Consortium."""; :domain kb:ED; :label "ED.language"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment """The reference is a telecommunication address (TEL), such as a URL for HTTP or FTP, that will resolve to precisely the same binary data that could as well have been provided as inline data. The semantic value of an encoded data value is the same, regardless whether the data is present inline data or just by-reference. However, an encoded data value without inline data behaves differently, since any attempt to examine the data requires the data to be downloaded from the reference. An encoded data value may have both inline data and a reference. The reference must point to the same data as provided inline. By-reference encoded data may not be allowed depending on the attribute or component that is declared encoded data. Character strings (see Section 4.3) must always be inline."""; :domain kb:ED; :label "ED.reference"; :range kb:TEL . a rdf:Property; a:maxCardinality "1"; :comment """A thumbnail is an abbreviated rendition of the full data. A thumbnail requires significantly fewer resources than the full data, while still maintaining some distinctive similarity with the full data. A thumbnail is typically used with by-reference encoded data. It allows a user to select data more efficiently before actually downloading through the reference. Thumbnails may not be allowed depending on the attribute or component that is declared encoded data. Character strings never have thumbnails, and a thumbnail may not itself contain a thumbnail.The ITS should consider the case where the thumbnail and the original both have the same properties of type, charset and compression. In this case, these properties need not be represented explicitly for the thumbnail but might be "inherited" from the main encoded data value to its thumbnail. Rationale: Originally, the term thumbnail refers to an image in a lower resolution (or smaller size) than another image. However, the thumbnail concept can be metaphorically used for media types other than images. For example, a movie may be represented by a shorter clip; an audio-clip may be represented by another audio-clip that is shorter, has a lower sampling rate, or a lossy compression."""; :domain kb:ED; :label "ED.thumbnail"; :range kb:ED . a rdf:Property; a:maxCardinality "1"; :comment """The encoded data�s type property identifies the encoding of the data and identifies a method to interpret or render the data. The domain of the encoded data�s type property is the MIME media types, defined by the Internet Assigned Numbers Authority (IANA). The encoded data�s type is a mandatory property, i.e., every non-NULL instance of encoded data must have a defined type property. The IANA defined domain of media types is established by the Internet standard RFC 2046 [ftp://ftp.isi.edu/in-notes/rfc2046.txt]. RFC 2046 defines the media type to consist of two parts: 1. top level media type, and 2. media subtype. However, this specification treats the entire media type as one atomic code symbol in the form defined by IANA, i.e., top level type followed by a slash "/" followed by media subtype. Currently defined media types are registered in a database [http://www.isi.edu/in-notes/iana/assignments/media-types] maintained by IANA. Currently more than 160 different MIME media types are defined, with the list growing rapidly. In general, all those types defined by the IANA may be used. To prevent the interoperability-problems associated with this diversity, this specification prefers certain media types to others. This is to define a greatest common denominator on which interoperability is not only possible, but that is powerful enough to support even advanced multimedia communication needs. (see the full text of the HL7 v3 data type semantics specification.)"""; :domain kb:ED; :label "ED.type"; :range kb:CS . kb:EIVL a :Class; :comment """The event-related periodic interval of time allows specifying a periodic interval of time based on activities of daily living, important events that are time-related but not fully determined by time. For example, "one hour after breakfast" specifies the beginning of the interval at one hour after breakfast is finished. Breakfast is assumed to occur before lunch but is not determined to occur at any specific time."""; :label "EIVL"; :subClassOf . a rdf:Property; a:maxCardinality "1"; a:values , , , , , , , , , , , , ; :comment """The event is a common (periodical) activity of daily living based on which the event related periodic interval is specified. Such events qualify for being adopted in the domain of this attribute for which all of the following is true: - the event commonly occurs on a regular basis, - the event is being used for timing activities, and - the event is not entirely determined by time. Examples are: the hour of sleep (HS), before meal (AC), after meal (PC), etc."""; :domain kb:EIVL; :label "EIVL.event"; :range kb:CV . a rdf:Property; a:maxCardinality "1"; :comment """The offset is an interval that marks the offsets for the beginning, width and end of the event-related periodic interval measured from the time each such event actually occurred. For example: if the specification is "one hour before breakfast for 10 minutes" the offset�s low boundary is -1 h and the offset�s width is 10 min (consequently the offset�s high boundary is -50 min.)"""; :domain kb:EIVL; :label "EIVL.offset"; :range kb:IVL . kb:EN a :Class; :comment """An entity name data value specifies a name of a person, organization, place or thing. Examples for entity name values are "Jim Bob Walton, Jr.", "Health Level Seven, Inc.", "Lake Tahoe", etc. An entity name may be as simple as a character string or may consist of several entity name parts (ENXP), such as, "Jim", "Bob", "Walton", and "Jr.", "Health Level Seven" and "Inc.", "Lake" and "Tahoe". The entity name data type is essentially a sequence of entity name part values."""; :label "EN"; :subClassOf . a rdf:Property; a:maxCardinality "1"; :comment "A code indicating the reason for which the name is used. Includes the following: normal (the name normally used), license (encompassing birth certificates, school records, degrees and titles, licenses, etc.), artist (encompassing stage names, pseudonyms/writer names), indigenous/tribal, religious."; :domain kb:EN; :label "EN.use_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment "This additional component will allow an interval of time to be associated with the entity name being described by the data type. This should be an optional component."; :domain kb:EN; :label "EN.valid_time"; :range . kb:ENXP a :Class; :comment "An entity name part is a character string token that may have a type code signifying the role of the part in the whole entity name. Typical name parts that exist in about every name are given names, and family names, titles, etc."; :label "ENXP"; :subClassOf kb:ST . a rdf:Property; a:maxCardinality "1"; :comment "Each name part may have a qualifier. The qualifier is a set of codes each of which specifies a certain subcategory of the name part in addition to the main name part type. For example, a given name may be flagged as a nickname, a family name may be a pseudonym or a name of public records."; :domain kb:ENXP; :label "ENXP.qualifier"; :range . a rdf:Property; a:maxCardinality "1"; :comment "A code indicating the reason for which the name is used. Includes the following: normal (the name normally used), license (encompassing birth certificates, school records, degrees and titles, licenses, etc.), artist (encompassing stage names, pseudonyms/writer names), indigenous/tribal, religious."; :domain kb:ENXP; :label "ENXP.use_cd"; :range kb:CS . kb:EditStatus a :Class; :label "EditStatus"; :subClassOf kb:HL7VocabularyConcept . kb:Employee a :Class; :comment "A relationship between a person or organization and a person or organization formed for the purpose of exchanging work for compensation. The purpose of the role is to identify the type of relationship the employee has to the employer, rather than the nature of the work actually performed. (Contrast with Assigned_entity)"; :label "Employee"; :subClassOf kb:Role . a rdf:Property; a:maxCardinality "1"; :comment "The type of hazards associated with the work performed by the employee for the employer. For example, asbestos, infectious agents."; :domain kb:Employee; :label "Employee.hazard_exposure_txt"; :range kb:ED . a rdf:Property; a:maxCardinality "1"; :comment """A code describing the job performed by the employee for the employer. For example, accountant, programmer, banker. Rationale: Represents the first component of the JCC data type (job Code)"""; :domain kb:Employee; :label "Employee.job_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; a:values , ; :comment """A code depicting the time-relative nature of the work performed by the employee for the employer. For example, full-time, part time. Rationale: The job class in v2.3 (second component of JCC data type) references Employee Classification table. The first component of the JCC data type (job code) is represented in Person_employment.job_cd."""; :domain kb:Employee; :label "Employee.job_class_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment "The title of the job held, for example, Vice President, Senior Technical Analyst."; :domain kb:Employee; :label "Employee.job_title_nm"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; :comment "Protective equipment needed for the job performed by the employee for the employer. For example, safety glasses, hard hat."; :domain kb:Employee; :label "Employee.protective_equipment_txt"; :range kb:ED . a rdf:Property; a:maxCardinality "1"; :comment """The salary amount paid by the employer to the employee. OpenIssue: Is this the amount paid per the value specified in salary_type_cd?"""; :domain kb:Employee; :label "Employee.salary_qty"; :range kb:MO . a rdf:Property; a:maxCardinality "1"; :comment "A code categorizing the calculation method used by the employer to compute the employee�s salary. For example, hourly, annual, commission."; :domain kb:Employee; :label "Employee.salary_type_cd"; :range kb:CE . kb:EmployeeJobClass a :Class; :label "EmployeeJobClass"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "EmployeeJobClass.FT"; :subClassOf kb:EmployeeJobClass . a kb:CE; ; :label "EmployeeJobClass.PT"; :subClassOf kb:EmployeeJobClass . kb:EncounterAccident a :Class; :label "EncounterAccident"; :subClassOf kb:HL7VocabularyConcept . kb:EncounterAdmissionSource a :Class; :label "EncounterAdmissionSource"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "EncounterAdmissionSource.E"; :subClassOf kb:EncounterAdmissionSource . a kb:CE; ; :label "EncounterAdmissionSource.LD"; :subClassOf kb:EncounterAdmissionSource . a kb:CE; ; :label "EncounterAdmissionSource.NB"; :subClassOf kb:EncounterAdmissionSource . kb:EncounterAdmissionUrgency a :Class; :label "EncounterAdmissionUrgency"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "EncounterAdmissionUrgency.EL"; :subClassOf kb:EncounterAdmissionUrgency . a kb:CE; ; :label "EncounterAdmissionUrgency.EM"; :subClassOf kb:EncounterAdmissionUrgency . a kb:CE; ; :label "EncounterAdmissionUrgency.UR"; :subClassOf kb:EncounterAdmissionUrgency . kb:EncounterReferralSource a :Class; :label "EncounterReferralSource"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "EncounterReferralSource.CREF"; :subClassOf kb:EncounterReferralSource . a kb:CE; ; :label "EncounterReferralSource.ER"; :subClassOf kb:EncounterReferralSource . a kb:CE; ; :label "EncounterReferralSource.HREF"; :subClassOf kb:EncounterReferralSource . a kb:CE; ; :label "EncounterReferralSource.LENF"; :subClassOf kb:EncounterReferralSource . a kb:CE; ; :label "EncounterReferralSource.PREF"; :subClassOf kb:EncounterReferralSource . a kb:CE; ; :label "EncounterReferralSource.THSP"; :subClassOf kb:EncounterReferralSource . a kb:CE; ; :label "EncounterReferralSource.TOHCF"; :subClassOf kb:EncounterReferralSource . a kb:CE; ; :label "EncounterReferralSource.TSNF"; :subClassOf kb:EncounterReferralSource . a kb:CE; ; :label "EncounterReferralSource.WI"; :subClassOf kb:EncounterReferralSource . kb:EncounterSpecialCourtesy a :Class; :label "EncounterSpecialCourtesy"; :subClassOf kb:HL7VocabularyConcept . a ; ; :label "EncounterSpecialCourtesy.EXT"; :subClassOf kb:EncounterSpecialCourtesy . a ; ; :label "EncounterSpecialCourtesy.NRM"; :subClassOf kb:EncounterSpecialCourtesy . a ; ; :label "EncounterSpecialCourtesy.PRF"; :subClassOf kb:EncounterSpecialCourtesy . a ; ; :label "EncounterSpecialCourtesy.STF"; :subClassOf kb:EncounterSpecialCourtesy . a ; ; :label "EncounterSpecialCourtesy.VIP"; :subClassOf kb:EncounterSpecialCourtesy . kb:Entity a :Class; :comment """A class or specific instance of a physical thing or an organization/group of physical things capable of participating in Acts; an artifact. This includes living subjects, organizations, material, and places. The Entity hierarchy encompasses human beings, organizations, living organisms, devices, pharmaceutical substances, etc. It does not include events/acts/actions, or the roles that things can play (e.g. patient, provider)."""; :label "Entity"; :subClassOf kb:HL7RIM . a rdf:Property; a:maxCardinality "1"; a:values , ; :comment """A code specifying which particular kind of Entity the Entity represents within its class The values for this attribute are drawn from one of several coding systems depending on the class of entities, such as living subjects (typed by animal and plant taxonomies), chemical substance (e.g., IUPAC code), organizations, insurance company, government agency, hospital, park, lake, syringe, etc. Note that Entity.cd may be so fine grained that some types may only have one known instance. Types with an extension of one instance are very similar to names. An example is the CDC vaccine manufacturer code, which is modeled as a concept vocabulary, when in fact each concept refers to only one instance."""; :domain kb:Entity; :label "Entity.cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; a:values ; :comment "A code specifying the class or category of Entities that the specific Entity represents. The code indicates which class in the Entity hierarchy is represented by any instance of Entity."; :domain kb:Entity; :label "Entity.class_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment """A textual or multimedia depiction of the Entity. The content of the description is not considered part of the functional information communicated between systems. Descriptions are meant to be shown to interested human individuals. All information relevant for automated functions must be communicated using the proper attributes and associated objects."""; :domain kb:Entity; :label "Entity.desc"; :range kb:ED . a rdf:Property; a:maxCardinality "1"; a:values , ; :comment "A code specifying whether Entity represents a class of artifacts or a specific instance of an artifact."; :domain kb:Entity; :label "Entity.determiner_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment "An interval of time specifying the period during which the artifact represented by Entity has, had, or will have physical existence."; :domain kb:Entity; :label "Entity.existence_time"; :range . a rdf:Property; a:maxCardinality "1"; a:values , , , , , , , , , , , , , , , , , ; :comment """A code specifying special handling requirements for the artifact represented by Entity. A code to describe how the Entity needs to be handled to avoid damage to it or other entities. Examples include: Keep at room temperature; Keep frozen below 0 C; Keep in a dry environment; Keep upright, do not turn upside down."""; :domain kb:Entity; :label "Entity.handling_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment """A unique identifier for the Entity. Communication only requires that each entity might have a single identifier assigned to it. Nevertheless, , since different systems will maintain different data bases, there may be different instance identifiers assigned by different systems. Note that an instance identifier is a pure identifier and not a classifier. For Material, serial numbers assigned by specific manufacturers, catalog numbers of specific distributors, or inventory numbers issued by owners, may also be represented by the Role.id, which allows a more clear expression of the fact that such a code is assigned by a specific party associated with that material."""; :domain kb:Entity; :label "Entity.id"; :range . a rdf:Property; a:maxCardinality "1"; :comment """A textual description or multimedia depiction of the relative importance the artifact represented by Entity has to the owner of the Entity. OpenIssue: There is a problem with this attribute. Shouldn't it be coded? Does it belong here at all?"""; :domain kb:Entity; :label "Entity.importance_status_txt"; :range kb:ED . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid266"; :domain kb:Entity; :label "Entity.is_played_by"; :range kb:Role . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid270"; :domain kb:Entity; :label "Entity.is_scoped_by"; :range kb:Role . a rdf:Property; a:maxCardinality "1"; :comment "A name for the Entity instance."; :domain kb:Entity; :label "Entity.nm"; :range . a rdf:Property; a:maxCardinality "1"; :comment """Specifies the quantity of the given entity, as interpreted in coordination with the determiner_cd. For individual instances of Entities, the qty is 1. For a group of individual members, the qty is the number of individual members in the group. When the Entity instance is a portion of a substance, the qty specifies the amount of that substance comprised by that portion. For an undetermined substance (kind) the qty servers two purposes at the same time: (a) it provides a means of relations between quantities specific for that substance, and (b) it is a reference quantity for the specification of ingredients or components. In all cases, the qty is an extensive "amount" kind of quantity (e.g., number, length, volume, mass, surface are, energy, etc.) Note that most relative or fractional quantities are not amounts, in particular, mass fraction, substance concentration, mass ratios, percentages, etc. are not extensive quantities and are prohibited values for this attribute. With undetermined kinds, the qty is but a reference quantity for the specification of the proportion of ingredients or components (e.g. through a has-part, has-ingredient, or has-content Role.) For example, a kind of group with 60% females is Person(qty = 100) has-part Person(qty = 60; sex = female). Amoxicillin 500 mg per tablet is Material(Tablet, qty = 1) has-ingredient Material(Amoxicillin, qty = 500 mg). Glucose 50% (D5W) is Material(D5W, qty = 1 kg) has-ingredient Material(Glucose, qty = 50 g). Material-specific quantity relations are expressed using the fact that the data type of this attribute is a set of physical quantity (SET_PQ>). If more than one qty value are specified in this set, each element in this set is considered to specify the same amount of the material. For example, for one liter of water one could use the set 1 L, 1 kg, 55.56 mol to specify the volume, mass, and amount of substance for the same amount of water, this is equivalent with specifying the mass density (volumic mass 1 kg/L) and the molar mass (18 g/mol). For Glucose one could specify 180 g, 1 mol according to the molar mass (180 g/mol)."""; :domain kb:Entity; :label "Entity.qty"; :range . a rdf:Property; a:maxCardinality "1"; a:values , , , , , , , , ; :comment "A code specifying the threat or hazard associated with the Entity."; :domain kb:Entity; :label "Entity.risk_cd"; :range kb:CE . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid276"; :domain kb:Entity; :label "Entity.served_by"; :range kb:Communication_function . a rdf:Property; a:maxCardinality "1"; a:values , ; :comment "A code specifying the state of Entity."; :domain kb:Entity; :label "Entity.status_cd"; :range . a rdf:Property; a:maxCardinality "1"; :comment "A telecommunication address for the Entity."; :domain kb:Entity; :label "Entity.telecom"; :range . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid272"; :domain kb:Entity; :label "Entity.used_by"; :range kb:Language_communication . kb:EntityClass a :Class; :label "EntityClass"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "EntityClass.ANM"; :subClassOf . a kb:CS; ; :label "EntityClass.CER"; :subClassOf . a kb:CS; ; :label "EntityClass.CHEM"; :subClassOf . a kb:CS; ; :label "EntityClass.ContainerEntityClass "; :subClassOf . a kb:CS; ; :label "EntityClass.DeviceEntityClass "; :subClassOf . a kb:CS; ; :label "EntityClass.EntityRootClass"; :subClassOf kb:EntityClass . a kb:CS; ; :label "EntityClass.FOOD"; :subClassOf . a kb:CS; ; :label "EntityClass.HOLD"; :subClassOf . a kb:CS; ; :label "EntityClass.LivingSubjectEntityClass "; :subClassOf . a kb:CS; ; :label "EntityClass.MIC"; :subClassOf . a kb:CS; ; :label "EntityClass.MODDV"; :subClassOf . a kb:CS; ; :label "EntityClass.ManufacturedMaterialEntityClass "; :subClassOf . a kb:CS; ; :label "EntityClass.MaterialEntityClass "; :subClassOf . a kb:CS; ; :label "EntityClass.NonPersonLivingSubjectEntityClass "; :subClassOf . a kb:CS; ; :label "EntityClass.OrganizationEntityClass "; :subClassOf . a kb:CS; ; :label "EntityClass.PLC"; :subClassOf . a kb:CS; ; :label "EntityClass.PLNT"; :subClassOf . a kb:CS; ; :label "EntityClass.PSN"; :subClassOf . a kb:CS; ; :label "EntityClass.PUB"; :subClassOf . a kb:CS; ; :label "EntityClass.RGRP"; :subClassOf . a kb:CS; ; :label "EntityClass.STATE"; :subClassOf . kb:EntityCode a :Class; :label "EntityCode"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "EntityCode.ACDA"; :subClassOf . a kb:CE; ; :label "EntityCode.ACDB"; :subClassOf . a kb:CE; ; :label "EntityCode.ACET"; :subClassOf . a kb:CE; ; :label "EntityCode.AINJ"; :subClassOf . a kb:CE; ; :label "EntityCode.AMIES"; :subClassOf . a kb:CE; ; :label "EntityCode.AMP"; :subClassOf . a kb:CE; ; :label "EntityCode.APLCTR"; :subClassOf . a kb:CE; ; :label "EntityCode.AccessMedicalDevice"; :subClassOf . a kb:CE; ; :label "EntityCode.AdministrationMedicalDevice"; :subClassOf . a kb:CE; ; :label "EntityCode.BACTM"; :subClassOf . a kb:CE; ; :label "EntityCode.BAG"; :subClassOf . a kb:CE; ; :label "EntityCode.BED"; :subClassOf . a kb:CE; ; :label "EntityCode.BF10"; :subClassOf . a kb:CE; ; :label "EntityCode.BLDG"; :subClassOf . a kb:CE; ; :label "EntityCode.BOR"; :subClassOf . a kb:CE; ; :label "EntityCode.BOTA"; :subClassOf . a kb:CE; ; :label "EntityCode.BOTD"; :subClassOf . a kb:CE; ; :label "EntityCode.BOTG"; :subClassOf . a kb:CE; ; :label "EntityCode.BOTPLY"; :subClassOf . a kb:CE; ; :label "EntityCode.BOUIN"; :subClassOf . a kb:CE; ; :label "EntityCode.BOX"; :subClassOf . a kb:CE; ; :label "EntityCode.BSKN"; :subClassOf . a kb:CE; ; :label "EntityCode.BlisterPackEntityType "; :subClassOf . a kb:CE; ; :label "EntityCode.BottleEntityType "; :subClassOf . a kb:CE; ; :label "EntityCode.C32"; :subClassOf . a kb:CE; ; :label "EntityCode.C38"; :subClassOf . a kb:CE; ; :label "EntityCode.CAN"; :subClassOf . a kb:CE; ; :label "EntityCode.CARD"; :subClassOf . a kb:CE; ; :label "EntityCode.CARS"; :subClassOf . a kb:CE; ; :label "EntityCode.CART"; :subClassOf . a kb:CE; ; :label "EntityCode.CARY"; :subClassOf . a kb:CE; ; :label "EntityCode.CHLTM"; :subClassOf . a kb:CE; ; :label "EntityCode.CNSTR"; :subClassOf . a kb:CE; ; :label "EntityCode.CTAD"; :subClassOf . a kb:CE; ; :label "EntityCode.ClinicalDrug"; :subClassOf . a kb:CE; ; :label "EntityCode.CompliancePackageEntityType "; :subClassOf . a kb:CE; ; :label "EntityCode.ContainerEntityType"; :subClassOf . a kb:CE; ; :label "EntityCode.DIALPK"; :subClassOf . a kb:CE; ; :label "EntityCode.DISK"; :subClassOf . a kb:CE; ; :label "EntityCode.DOSET"; :subClassOf . a kb:CE; ; :label "EntityCode.DSKS"; :subClassOf . a kb:CE; ; :label "EntityCode.DSKUNH"; :subClassOf . a kb:CE; ; :label "EntityCode.DrugEntity"; :subClassOf . a kb:CE; ; :label "EntityCode.EDTK15"; :subClassOf . a kb:CE; ; :label "EntityCode.EDTK75"; :subClassOf . a kb:CE; ; :label "EntityCode.EDTN"; :subClassOf . a kb:CE; ; :label "EntityCode.ENT"; :subClassOf . a kb:CE; ; :label "EntityCode.F10"; :subClassOf . a kb:CE; ; :label "EntityCode.FDP"; :subClassOf . a kb:CE; ; :label "EntityCode.FL10"; :subClassOf . a kb:CE; ; :label "EntityCode.FL100"; :subClassOf . a kb:CE; ; :label "EntityCode.FLOOR"; :subClassOf . a kb:CE; ; :label "EntityCode.HCL6"; :subClassOf . a kb:CE; ; :label "EntityCode.HEPA"; :subClassOf . a kb:CE; ; :label "EntityCode.HEPL"; :subClassOf . a kb:CE; ; :label "EntityCode.HEPN"; :subClassOf . a kb:CE; ; :label "EntityCode.HNO3"; :subClassOf . a kb:CE; ; :label "EntityCode.IALINE"; :subClassOf . a kb:CE; ; :label "EntityCode.IVLINE"; :subClassOf . a kb:CE; ; :label "EntityCode.IndividualPackageEntityType"; :subClassOf . a kb:CE; ; :label "EntityCode.InhalerMedicalDevice "; :subClassOf . a kb:CE; ; :label "EntityCode.InjectionMedicalDevice"; :subClassOf . a kb:CE; ; :label "EntityCode.JAR"; :subClassOf . a kb:CE; ; :label "EntityCode.JKM"; :subClassOf . a kb:CE; ; :label "EntityCode.JUG"; :subClassOf . a kb:CE; ; :label "EntityCode.KARN"; :subClassOf . a kb:CE; ; :label "EntityCode.KOX"; :subClassOf . a kb:CE; ; :label "EntityCode.KitEntityType "; :subClassOf . a kb:CE; ; :label "EntityCode.LIA"; :subClassOf . a kb:CE; ; :label "EntityCode.LineAccessMedicalDevice "; :subClassOf . a kb:CE; ; :label "EntityCode.M4"; :subClassOf . a kb:CE; ; :label "EntityCode.M4RT"; :subClassOf . a kb:CE; ; :label "EntityCode.M5"; :subClassOf . a kb:CE; ; :label "EntityCode.MICHTM"; :subClassOf . a kb:CE; ; :label "EntityCode.MINIM"; :subClassOf . a kb:CE; ; :label "EntityCode.MMDTM"; :subClassOf . a kb:CE; ; :label "EntityCode.ManufacturedDrug"; :subClassOf . a kb:CE; ; :label "EntityCode.MaterialEntityAdditive"; :subClassOf . a kb:CE; ; :label "EntityCode.MaterialEntityClassType"; :subClassOf kb:EntityCode . a kb:CE; ; :label "EntityCode.MedicalDevice"; :subClassOf . a kb:CE; ; :label "EntityCode.MultiUseContainerEntityType"; :subClassOf . a kb:CE; ; :label "EntityCode.NAF"; :subClassOf . a kb:CE; ; :label "EntityCode.NEBAMP"; :subClassOf . a kb:CE; ; :label "EntityCode.NONE"; :subClassOf . a kb:CE; ; :label "EntityCode.NonRigidContainerEntityType"; :subClassOf . a kb:CE; ; :label "EntityCode.OVUL"; :subClassOf . a kb:CE; ; :label "EntityCode.PACKT"; :subClassOf . a kb:CE; ; :label "EntityCode.PAGE"; :subClassOf . a kb:CE; ; :label "EntityCode.PCH"; :subClassOf . a kb:CE; ; :label "EntityCode.PEN"; :subClassOf . a kb:CE; ; :label "EntityCode.PHENOL"; :subClassOf . a kb:CE; ; :label "EntityCode.PMP"; :subClassOf . a kb:CE; ; :label "EntityCode.PVA"; :subClassOf . a kb:CE; ; :label "EntityCode.PackageEntityType "; :subClassOf . a kb:CE; ; :label "EntityCode.PlaceEntityType"; :subClassOf kb:EntityCode . a kb:CE; ; :label "EntityCode.PlasticBottleEntityType "; :subClassOf . a kb:CE; ; :label "EntityCode.RLM"; :subClassOf . a kb:CE; ; :label "EntityCode.ROOM"; :subClassOf . a kb:CE; ; :label "EntityCode.RigidContainerEntityType"; :subClassOf . a kb:CE; ; :label "EntityCode.SACH"; :subClassOf . a kb:CE; ; :label "EntityCode.SILICA"; :subClassOf . a kb:CE; ; :label "EntityCode.SPS"; :subClassOf . a kb:CE; ; :label "EntityCode.SST"; :subClassOf . a kb:CE; ; :label "EntityCode.STUTM"; :subClassOf . a kb:CE; ; :label "EntityCode.SYR"; :subClassOf . a kb:CE; ; :label "EntityCode.SYSTM"; :subClassOf . a kb:CE; ; :label "EntityCode.THROM"; :subClassOf . a kb:CE; ; :label "EntityCode.THYMOL"; :subClassOf . a kb:CE; ; :label "EntityCode.THYO"; :subClassOf . a kb:CE; ; :label "EntityCode.TIN"; :subClassOf . a kb:CE; ; :label "EntityCode.TOLU"; :subClassOf . a kb:CE; ; :label "EntityCode.TRBINH"; :subClassOf . a kb:CE; ; :label "EntityCode.TUB"; :subClassOf . a kb:CE; ; :label "EntityCode.TUBE"; :subClassOf . a kb:CE; ; :label "EntityCode.URETM"; :subClassOf . a kb:CE; ; :label "EntityCode.VIAL"; :subClassOf . a kb:CE; ; :label "EntityCode.VIRTM"; :subClassOf . a kb:CE; ; :label "EntityCode.WEST"; :subClassOf . kb:EntityHandling a :Class; :label "EntityHandling"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "EntityHandling.AMB"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.C37"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.CAMB"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.CATM"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.CFRZ"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.CREF"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.DFRZ"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.DRY"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.FRZ"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.MTLF"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.NTR"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.PRTL"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.PSA"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.PSO"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.REF"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.SBU"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.UFRZ"; :subClassOf kb:EntityHandling . a kb:CE; ; :label "EntityHandling.UPR"; :subClassOf kb:EntityHandling . kb:EntityNamePartQualifier a :Class; :label "EntityNamePartQualifier"; :subClassOf kb:HL7VocabularyConcept . kb:EntityNamePartType a :Class; :label "EntityNamePartType"; :subClassOf kb:HL7VocabularyConcept . kb:EntityNameUse a :Class; :label "EntityNameUse"; :subClassOf kb:HL7VocabularyConcept . kb:EntityRisk a :Class; :label "EntityRisk"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "EntityRisk.AGG"; :subClassOf kb:EntityRisk . a kb:CE; ; :label "EntityRisk.BHZ"; :subClassOf . a kb:CE; ; :label "EntityRisk.BIO"; :subClassOf kb:EntityRisk . a kb:CE; ; :label "EntityRisk.COR"; :subClassOf kb:EntityRisk . a kb:CE; ; :label "EntityRisk.ESC"; :subClassOf kb:EntityRisk . a kb:CE; ; :label "EntityRisk.EXP"; :subClassOf . a kb:CE; ; :label "EntityRisk.INJ"; :subClassOf kb:EntityRisk . a kb:CE; ; :label "EntityRisk.MaterialDangerInfectious "; :subClassOf kb:EntityRisk . a kb:CE; ; :label "EntityRisk.MaterialDangerInflammable "; :subClassOf kb:EntityRisk . a kb:CE; ; :label "EntityRisk.POI"; :subClassOf kb:EntityRisk . a kb:CE; ; :label "EntityRisk.RAD"; :subClassOf kb:EntityRisk . kb:EntityStatus a :Class; :label "EntityStatus"; :subClassOf kb:HL7VocabularyConcept . a ; ; :label "EntityStatus.Active"; :subClassOf . a ; ; :label "EntityStatus.Normal"; :subClassOf kb:EntityStatus . a ; ; :label "EntityStatus.Nullified"; :subClassOf kb:EntityStatus . a ; ; :label "EntityStatus.Terminated"; :subClassOf . kb:Entity_heir a :Class; :comment """Rationale: It has been discovered that one cannot create an HMD choice structure for a set of classes, all of which are sub-types of Act, Role or Entity, but for which there is not a defined physical class. These are the classes that would have been in the RIM as direct descendants (heirs) of Act, Role and Entity, except for the fact that they carried no unique attributes or associations. The addition of this single empty class in each hierarchy will permit messages with the appropriate and necessary choice structures to be built. Subsequent evolution of the methodology and tooling may permit the elimination of these classes in favor of an equivalent abstraction in the methodology."""; :label "Entity_heir"; :subClassOf kb:Entity . kb:EquipmentAlertLevel a :Class; :label "EquipmentAlertLevel"; :subClassOf kb:HL7VocabularyConcept . kb:Ethnicity a :Class; :label "Ethnicity"; :subClassOf kb:HL7VocabularyConcept . a ; ; :label "Ethnicity.Hispanic"; :subClassOf kb:Ethnicity . a ; ; :label "Ethnicity.NotHispanicOrLatino"; :subClassOf kb:Ethnicity . kb:Financial_act a :Class; :comment "An act utilized primarily for administrative (versus clinical) purposes."; :label "Financial_act"; :subClassOf kb:Act . a rdf:Property; a:maxCardinality "1"; :comment """The monetary value of a financial act after any applicable discounts and adjustments have been applied. This attribute can be used to represent concepts that include the balance of a financial account, the value of a financial transaction, and the value of an invoice line item or adjustment."""; :domain kb:Financial_act; :label "Financial_act.net_amt"; :range kb:MO . kb:Financial_contract a :Class; :comment "A contract whose value is measured in monetary terms."; :label "Financial_contract"; :subClassOf kb:Act . a rdf:Property; a:maxCardinality "1"; a:values , , , ; :comment """Establishes the payment terms for a contractual agreement or obligation. Examples are "net 30", "on receipt of invoice", "upon completion of service", etc."""; :domain kb:Financial_contract; :label "Financial_contract.payment_terms_cd"; :range kb:CE . kb:Financial_transaction a :Class; :comment """A sub-class of Act representing any transaction between two accounts whose value is measured in monetary terms. In the "intent" mood, communicates a request for a transaction to be initiated, or communicates a transfer of value between two accounts. In the "event" mood, communicates the posting of a transaction to an account."""; :label "Financial_transaction"; :subClassOf kb:Financial_act . a rdf:Property; a:maxCardinality "1"; :comment """A decimal number indicating the rate of exchange in effect between the currency of the account being credited, and the currency of the transaction value. For example, for the purchase of services valued in Mexican pesos using U.S. dollars paid from a Canadian dollar account, the credit exchange ratio would be communicated as real number "r" such that "y (USD) * r = x (CAD)". Rationale: this approach ensures that a common reporting mechanism is used, from the perspective of the value of the transaction, which is used to communicate the value of the act."""; :domain kb:Financial_transaction; :label "Financial_transaction.credit_exchange_rate_qty"; :range kb:REAL . a rdf:Property; a:maxCardinality "1"; :comment """A decimal number indicating the rate of exchange in effect between the currency of the account being debited, and the currency of the transaction value. For example, for the purchase of services valued in Mexican pesos using U.S. dollars paid from a Canadian dollar account, the debit exchange ratio would be communicated as real number "r" such that "y (USD) * r = x (MXP)". Rationale: this approach ensures that a common reporting mechanism is used, from the perspective of the value of the transaction, which is used to communicate the value of the act."""; :domain kb:Financial_transaction; :label "Financial_transaction.debit_exchange_rate_qty"; :range kb:REAL . a rdf:Property; a:maxCardinality "1"; :comment """A ratio that indicates the rate of interest that the transaction value is subject to and the term over which the interest rate compounds. The numerator is the interest rate and the denominator is the compounding term."""; :domain kb:Financial_transaction; :label "Financial_transaction.interest_rate_qty"; :range kb:RTO . kb:GTS a :Class; :comment """The general timing specification (GTS) semantically is a general set of points in time. The purpose of the GTS is to specify the complex timing of events and actions (mainly in orders and scheduling systems.) The GTS also supports the cyclical validity patterns that may exist for certain kinds of information, such as phone numbers (evening, daytime), addresses (so called "snowbirds," residing in the south during winter and north during summer) and office hours. The GTS data type has the following aspects: - GTS as a general set of points in time (SET?TS?). From this aspect GTS answers whether any given point in time falls in the timing covered by the GTS value. - GTS as the combination of multiple periodic intervals of time. This aspect describes how both simple and complex repeat-patterns are specified with the GTS. - GTS as a generator of a sequence of intervals of point in time (LIST?IVL?TS??). From this aspect, GTS can generate all occurrence intervals of an event or action, or all validity periods for a fact. - GTS as an expression-syntax defined for a calendar. This aspect is the GTS literal form. The GTS data type is defined as using intervals, periodic intervals, and event-related periodic intervals."""; :label "GTS"; :subClassOf . kb:GTSAbbreviation a :Class; :label "GTSAbbreviation"; :subClassOf kb:HL7VocabularyConcept . kb:GenderStatus a :Class; :label "GenderStatus"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "GenderStatus.I"; :subClassOf kb:GenderStatus . a kb:CE; ; :label "GenderStatus.N"; :subClassOf kb:GenderStatus . kb:Guarantor a :Class; :comment "The double role-based association between a party in the role of guarantor and an organization in the role of healthcare provider ."; :label "Guarantor"; :subClassOf kb:Role . a rdf:Property; a:maxCardinality "1"; :comment "A code depicting the credit rating (e.g., excellent, good, fair, questionable, poor)."; :domain kb:Guarantor; :label "Guarantor.credit_rating_cd"; :range kb:CE . kb:HIST a :Class; :comment """SET_HXIT This generic data type is used to collect an entire history of any other data value. A history is a non-empty set of data values that conform to the history item (HXIT) type, i.e., data values that have a valid-time property. The history information is not limited to the past; expected future values can also appear. The earliest history item is the item in the set whose valid time�s low boundary (validity start time) is less or equal (i.e. before) that of any other history item in the set. Likewise, the latest history item is the item in the set whose valid time�s high boundary (validity end time) is greater or equal (i.e. after) that of any other history item in the set. The semantics does not principally forbid the time intervals to overlap. However, if two history items have the same low (high) boundary in the valid time interval, it is undefined which one is considered the earliest (latest). Except earliest is the derived history that has the earliest item excluded. Except latest is the derived history that has the latest item excluded. A type conversion exists between an entire history HIST and a single history item HXIT. This conversion takes the latest data from the history. The purpose of this conversion is to allow an information producer to produce a history of any value instead of sending just one value. An information-consumer, who does not expect a history but a simple value, will convert the history to the latest value. Note from the definition of history item (HXIT) below, that HXIT semantically extends T. This means, that the information-consumer expecting a T but given an HXIT will not recognize any difference (substitutability of specializations.) ITS Note: the order of history items in the lists should be backwards in time."""; :label "HIST"; :subClassOf kb:SET . a rdf:Property; :label "HIST.members"; :range kb:HXIT . kb:HL7CommiteeIDInRIM a :Class; :label "HL7CommiteeIDInRIM"; :subClassOf kb:HL7VocabularyConcept . kb:HL7ConformanceInclusion a :Class; :label "HL7ConformanceInclusion"; :subClassOf kb:HL7VocabularyConcept . kb:HL7DefinedRoseProperty a :Class; :label "HL7DefinedRoseProperty"; :subClassOf kb:HL7VocabularyConcept . kb:HL7RIM a :Class; :comment """Based on HL7 RIM v 1.15 Modeling Decisions -- All HL7 datatypes are modeled as classes in Protege-2000 -- All HL7 datatype Protege-2000 classes are modeled as instances of HL7_Data_Type metaclass -- Instances of Concept Descriptors (CD) are concepts that can be organized in classification hierarchy. Thus the datatypes CD and its subclasses are modeled as Protege-200 metaclasses, whose instances are classes -- Protege-2000 doesn't support template constructs such as set, list, bag, and interval. Each template is modeled as a class with a 'members' slot. Instantiations of templates with specific classes are modeled as subclasses of template classes, where the allowed values of the members slot are constrained to be instances of specific classes. -- HL7 practice of 'restricting' a subclass by making certain attributes not applicable for the class is modeled in Protege as a subclass where these attributes are constrained to have cardinality zero. -- Associations and attributes of HL7 classes are all slots of Protege-2000 classes"""; :label "HL7RIM"; :subClassOf :Resource . kb:HL7UpdateMode a :Class; :label "HL7UpdateMode"; :subClassOf kb:HL7VocabularyConcept . kb:HL7VocabularyConcept a :Class; a:role "abstract"; :comment """Based on HL7 Vocabulary Domains v 1.15 Modeling Decisions -- All HL7 vocabulary domain values are modeled as classes in Protege-2000 ---In order to preserve the hierarchy between vocabulary values, the lower values are modeled under the higher values as child classes. --In order to maintain the relationship between HL7 data types and the vocabulary values, the vocabulary values have been implemented as instances of the data types. --Not all vocabulary domains have values associated with them. Also in some domains values have been populated only till the second level and not all the fields (like mnemonic code etc.) for the values have been populated either. """; :label "HL7VocabularyConcept"; :subClassOf :Resource . a rdf:Property; a:maxCardinality "1"; a:values "Level 0", "Level 1", "Level 2", "Level 3"; :label "HL7VocabularyConcept.level"; :range :Literal . kb:HL7_Data_Type a :Class; :label "HL7_Data_Type"; :subClassOf :Class . kb:HL7_Data_Value a :Class; :label "HL7_Data_Value"; :subClassOf :Class . kb:HXIT a :Class; :comment """History_item. This generic data type extension is tags a time range to its base data value. The time range is the time in which that data was, is, or is expected to be valid. If the base type T does not possess a valid time property, the HXIT adds that property to the base type. If, however, the base type T does have a valid time property, that property can be mapped to the valid time property of the HXIT. Note that data types are specifications of abstract properties of values. This specification does not mandate how these values are represented in an ITS or implemented in an application. Specifically, it does not mandate how the represented components are named or positioned. In addition, the semantic generalization hierarchy may be different from a class hierarchy chosen for implementation (if the implementation technology has inheritance.) Keep the distinction between a type (interface) and an implementation (concrete data structure, class) in mind. The ITS must contain a mapping of ITS defined features of any data type to the semantic properties defined here."""; :label "HXIT"; :subClassOf kb:T . a rdf:Property; a:maxCardinality "1"; :comment "The time interval during which the given information was, is, or is expected to be valid. The interval can be open or closed infinite or undefined on either side."; :domain kb:HXIT; :label "HXIT.validTime"; :range . kb:HtmlLinkType a :Class; :label "HtmlLinkType"; :subClassOf kb:HL7VocabularyConcept . a ; ; :label "HtmlLinkType.alternate"; :subClassOf kb:HtmlLinkType . a ; ; :label "HtmlLinkType.appendix"; :subClassOf kb:HtmlLinkType . a ; ; :label "HtmlLinkType.bookmark"; :subClassOf kb:HtmlLinkType . a ; ; :label "HtmlLinkType.chapter"; :subClassOf kb:HtmlLinkType . a ; ; :label "HtmlLinkType.contents"; :subClassOf kb:HtmlLinkType . a ; ; :label "HtmlLinkType.copyright"; :subClassOf kb:HtmlLinkType . a ; ; :label "HtmlLinkType.glossary"; :subClassOf kb:HtmlLinkType . a ; ; :label "HtmlLinkType.help"; :subClassOf kb:HtmlLinkType . a ; ; :label "HtmlLinkType.index"; :subClassOf kb:HtmlLinkType . a ; ; :label "HtmlLinkType.next"; :subClassOf kb:HtmlLinkType . a ; ; :label "HtmlLinkType.prev"; :subClassOf kb:HtmlLinkType . a ; ; :label "HtmlLinkType.section"; :subClassOf kb:HtmlLinkType . a ; ; :label "HtmlLinkType.start"; :subClassOf kb:HtmlLinkType . a ; ; :label "HtmlLinkType.stylesheet"; :subClassOf kb:HtmlLinkType . a ; ; :label "HtmlLinkType.subsection"; :subClassOf kb:HtmlLinkType . kb:II a :Class; :comment "The Instance Identifier (II) data type is used to uniquely identify an instance, thing or object. Examples are object identifier for HL7 RIM objects, medical record number, order id, service catalog item id, etc. Instance identifiers are defined based on ISO object identifiers."; :label "II"; :subClassOf kb:ANY . a rdf:Property; a:maxCardinality "1"; :comment """This is a human readable name or mnemonic for the assigning authority. This name is provided solely for the convenience of unaided humans interpreting an II value. The assigning authority name need not be unique or globally meaningful. Note: no automated processing must depend on the assigning authority name to be present in any form. The assigning authority name is not the name for the individually identified object, but for the namespace, that immediately contains that object identifier. Two cases exist. 1) If the extension property is non-NULL, the root OID identifies the assigning authority, hence the assigning authority name is a name or mnemonic for the entire root OID. 2) If the extension is NULL, the assigning authority name is the name or mnemonic of the namespace property of the OID value."""; :domain kb:II; :label "II.assigningAuthorityName"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; :comment """A character string value of the identifier. The extension must be unambiguous (unique) within the domain of the root OID. The extension property may be NULL in which case the root OID is the complete unique identifier. It is recommended that systems use the OID scheme for external identifiers of their communicated objects. The extension property is mainly provided to accommodate legacy alphanumeric identifier schemes. Open Issue: the 3-2-4 grouping in U.S. social security numbers is pure decoration and has no meaning. Some systems save space not storing the dashes and may not fill in the dashes when sending social security numbers. This means, that equivalence of two identifiers may be weaker than the equivalence of the extensions as character strings. For example, a system may has to consider the SSNs "123456789" and "123-45-6789" to be equivalent. It is therefore recommended to strip off all decorating meaningless characters when comparing extensions. However, what constitutes a meaningless character is entirely dependent upon the identifier scheme identified in the root property. Since social security numbers are numeric strings, they could also be assigned to the end of an OID. This specification will be more restrictive in the future to reduce the number of different cases."""; :domain kb:II; :label "II.extension"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; a:minCardinality "1"; :comment """The root of an instance identifier guarantees the uniqueness of the identifier. The root alone may be the entire unique identifier, an extension value is not needed. In the presence of a non-null extension, the root is commonly interpreted as the "assigning authority", that is, it is supposed that the root OID somehow refers to an organization that assigns identifiers sent in the extension. However, the root does not have to be an organizational OID, it can also be and OID specifically registered for an identifier scheme. Rationale: DICOM objects are identified by OID only. For the purpose of DICOM/HL7 integration, it would be awkward if HL7 required the extension to be mandatory and to consider the OID only as an assigning authority. Since OID values are simpler and do not contain the risks of containing meaningless decoration, we do encourage systems to use simple OID identifiers as external references to their objects."""; :domain kb:II; :label "II.root"; :range kb:OID . a rdf:Property; a:maxCardinality "1"; :comment """The identifier is valid in this optional time-range. By default, the identifier is valid indefinitely. Any specific interval may be undefined on either side indicating unknown effective or expiry time. Note: identifiers for information objects in computer systems should not have restricted valid times, but should be globally unique at all times. The identifier valid time is provided mainly for real-world identifiers, whose maintenance policy may include expiry (e.g., credit card numbers.)"""; :domain kb:II; :label "II.validTime"; :range . kb:INT a :Class; :comment "Integer numbers are precise numbers that are results of counting and enumerating. Integer numbers are discrete, the set of integers is infinite but countable. No arbitrary limit is imposed on the range of integer numbers. Two exceptional values are defined for the positive and negative infinity."; :label "INT"; :subClassOf kb:QTY . a rdf:Property; a:maxCardinality "1"; a:range "integer"; :label "INT.value"; :range :Literal . kb:IVL a :Class; :comment """An interval is a set of consecutive values of any ordered data type. An interval is thus a continuous subset of its base data type. Any ordered type can be the basis of an interval. It does not matter whether the base type is discrete or continuous. If the base data type is only partially ordered, all elements of the interval must be elements of a totally ordered subset of the ordered data type. For example, physical quantities are considered ordered. However the ordering of physical quantities is only partial; a total order is only defined among comparable quantities (quantities of the same physical dimension.) While intervals between 2 and 4 meters exists, there is no interval between 2 meters and 4 seconds. Intervals are sets and have all the properties of sets. However, union and differences of intervals may not be intervals any more, since the elements of these union and difference sets may not be consecutive. Intersections of intervals are always intervals."""; :label "IVL"; :subClassOf kb:ANY . a rdf:Property; a:maxCardinality "1"; :comment "The center is defined of finite intervals and is then the arithmetic mean of the interval (low pus high divided by 2). The purpose of distinguishing the center as a semantic property is for conversions of intervals to point values. This is most relevant when intervals are used to express uncertainty."; :domain kb:IVL; :label "IVL.center"; :range kb:T . a rdf:Property; a:maxCardinality "1"; :comment "This is the upper boundary of the interval."; :domain kb:IVL; :label "IVL.high"; :range kb:T . a rdf:Property; a:maxCardinality "1"; :comment "Indicates whether the interval is closed or open at the high boundary. For a boundary to be closed, a finite boundary must be provided, i.e. unspecified or infinite boundaries are always open."; :domain kb:IVL; :label "IVL.highClosed"; :range kb:BL . a rdf:Property; a:maxCardinality "1"; :comment "This is the low boundary of the interval."; :domain kb:IVL; :label "IVL.low"; :range kb:T . a rdf:Property; a:maxCardinality "1"; :comment "Indicates whether the interval is closed or open at the low boundary. For a boundary to be closed, a finite boundary must be provided, i.e. unspecified or infinite boundaries are always open."; :domain kb:IVL; :label "IVL.lowClosed"; :range kb:BL . a rdf:Property; a:maxCardinality "1"; :comment """The width is the difference between high and low boundary. The purpose of distinguishing a width property is to handle all cases of incomplete information symmetrically. In any interval representation only two of the three properties high, low, and width need to be stated and the third can be derived. When both boundaries are known, width can be derived as high minus low. When one boundary and the width is known, the other boundary is also known. When no boundary is known, the width may still be known. For example, one knows that an activity takes about 30 minutes, but one may not yet know when that activity is started."""; :domain kb:IVL; :label "IVL.width"; :range kb:T . a :Class; :comment "Generic type instance: Interval of int."; :label "IVL_INT>"; :subClassOf kb:IVL . a :Class; :comment "Generic type instance: Interval of MO"; :label "IVL_MO>"; :subClassOf kb:IVL . a :Class; :comment "Generic type instance: Interval of pq."; :label "IVL_PQ>"; :subClassOf kb:IVL . a :Class; :comment "Generic type instance: Interval of time."; :label "IVL_TS>"; :subClassOf kb:IVL . kb:Imaging_modality a :Class; :comment "Class to contain unique attributes of diagnostic imaging equipment."; :label "Imaging_modality"; :subClassOf kb:Device . a rdf:Property; a:maxCardinality "1"; :comment "The relationship between the Pixel sample values and the X-Ray beam intensity."; :domain kb:Imaging_modality; :label "Imaging_modality.pixel_intensity_relationship_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment "Value of pixels added to non-rectangular image to pad to rectangular format."; :domain kb:Imaging_modality; :label "Imaging_modality.pixel_padding_qty"; :range kb:PQ . a rdf:Property; a:maxCardinality "1"; :comment "The inherent limiting resolution in mm of the equipment for high contrast objects for the data gathering and reconstruction technique chosen. If variable across the images of the series, the value at the image center."; :domain kb:Imaging_modality; :label "Imaging_modality.spacial_resolution_qty"; :range kb:PQ . kb:Invoice_element a :Class; :comment """A sub-type of Act that provides support for the full range of information requirements for invoice processing in healthcare. The class will be used in at least three moods - definition, order and event - and with a variety of both class_cd and cd values to distinguish them. In the "definition" mood, this class provides for the specification of component items covered by health insurance plans and policies. These items may in turn be linked to one or more billable acts in definition mood to specify the coverages. In the "order" mood, this class becomes an "invoice" (or claim) containing a set of items (also instances of this class), associated to the billable acts covered by the items and the policies under which the invoice is asserted, etc. When instances of this class exist in relationship with instances of authorization or eligibility, are used to communicate the details of requests for authorization or eligibility inquiries. In the "event" mood, this class represents the action (result) undertaken in response to the claim. This includes a set of processing results and adjustments instantiated from this class that reflect the specific coverage decisions related to each of the items in the ordered invoice. The context for this class is established, as usual, by a combination of act relationships, participations and roles which undertake the participations. Act relationships provide for: compositional relations between plans, policies and sub-policies; compositional relations between invoices, invoice item groups and invoice items; compositional relations between processing results and adjustments within a single result; and reference relationships between one invoice item and another or from a processing result (event) to the invoice item (order) to which it responds. Participation types used by this class include: "beneficiary," which reflects a "covered party" (role) as the target of a coverage policy or item, and which provides for coordination-of-benefits sequencing among a set of covered parties; and "policy holder" which is in the domain ServiceTargetType."""; :label "Invoice_element"; :subClassOf kb:Financial_act . a rdf:Property; a:maxCardinality "1"; :comment "A code depicting the source of information about the coverage (e.g., insurance company, employer, insured presented policy, insured presented card, signed statement on file, verbal information, none, . . .)."; :domain kb:Invoice_element; :label "Invoice_element.coverage_source_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment """Used in financial calculations to derive amounts from quantities of services delivered and/or goods received. The simplest formula for deriving gross amounts is: Units (Quantity) * Cost/Unit = Amount The concept of a Factor allows for a discount or surcharge multiplier to be applied to a monetary amount. For example, the formula, with a factor would be: Units (Quantity) * Cost/Point * Factor = Amount For example, this could be 10 (Number of Treatments as Units) * $3.00 (Cost per Unit) * 1.5 (Factor) = $45.00 (Amount). See related note on Points. Formula, with Points and Factors becomes: Units * Cost/Unit * Points * Factor = Amount"""; :domain kb:Invoice_element; :label "Invoice_element.factor_nbr"; :range kb:REAL . a rdf:Property; a:maxCardinality "1"; :comment """Designates a modifier to the cd attribute to provide additional information about the invoice element. In the "intent" mood, communicates processing consideration information. In the "event" mood, communicates information about sub-trees of the coding system utilized in the cd attribute for additional information, clarification, etc."""; :domain kb:Invoice_element; :label "Invoice_element.modifier_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment "A flag indicating whether the details of the invoice processing results (usually an authorization or an adjustment) should be communicated directly to the covered party involved."; :domain kb:Invoice_element; :label "Invoice_element.notify_subject_ind"; :range kb:BL . a rdf:Property; a:maxCardinality "1"; :comment """Used in financial calculations to derive amounts from quantities of services delivered and/or goods received. The simplest formula for deriving amounts is: Units (Quantity) * Cost/Unit = Amount The concept of Points allows for assignment of point values for services and/or goods, such that a dollar amount can be assigned to each point. For example, the formula, with points would be: Units (Quantity) * Points * Cost/Point = Amount For example, this could be 5 (Number of Treatments as Units) * 3 (Number of Points per treatment as Points)* $20.00 (Cost per Point) = $300.00 (Amount). See related note on Factor. Formula, with Points and Factors becomes: Units * Cost/Unit * Points * Factor = Amount"""; :domain kb:Invoice_element; :label "Invoice_element.points_nbr"; :range kb:REAL . a rdf:Property; a:maxCardinality "1"; :comment "The monetary cost per unit being accounted. In constructing the ratio, the numerator must of data type MO, and the denominator must be a PQ, specified in the same manner as the unit_qty attribute."; :domain kb:Invoice_element; :label "Invoice_element.unit_price_amt"; :range . a rdf:Property; a:maxCardinality "1"; :comment """A description of the number of instances of a product or service that is being billed or charged for.This attribute represents such concepts as 4 hours, 4 mg, 4 boxes, etc. The unit of measure is restricted to a measurable unit such as liters, milligrams and hours. Non-measurable, but countable units such as boxes, packages, visits must not be specified using the unit component of the PQ data type, except as an annotation, marked by {xxx}.Refer to Data Types Part II Unabridged Specification, Appendix A :Unified Code for Units of Measure. Specification of countable units can be handled with the following techniques: (1) specify the countable unit in the invoice_element.cd.That is, a specific Invoice_element.cd would indicate that the item referenced by the act represents a box of 20 items.There would be a different Invoice_element.cd for a box of 40 items, and so on. For example, if the Invoice_element.cd represents a box of 20 items, and the Invoice_element.unit_qty = 2 (no units), then this represents 2 boxes of 20 items for a total of 40 items. (2) if more detail is required (e.g. to describe the composition, packaging, manufacturer of a product), then use a participation (type_cd = "PRD"), and a combination of role and entity classes to describe the details. """; :domain kb:Invoice_element; :label "Invoice_element.unit_qty"; :range kb:PQ . kb:LIST a :Class; :label "LIST"; :subClassOf kb:ANY . a rdf:Property; :domain kb:LIST; :label "LIST.members"; :range kb:UVP . a :Class; :comment "Generic type instance: List of person address parts"; :label "LIST_ADXP>"; :subClassOf kb:LIST . a :Class; :comment "http://protege.stanford.edu/kb#genid803"; :label "LIST_ANY>"; :subClassOf kb:LIST . a :Class; :comment "Generic type instance:List of Boolean values (binary data)."; :label "LIST_BL>"; :subClassOf kb:LIST . a :Class; :comment "http://protege.stanford.edu/kb#genid761"; :label "LIST_CR>"; :subClassOf kb:LIST . a :Class; :comment "Generic type instance: List of entity name parts."; :label "LIST_ENXP>"; :subClassOf kb:LIST . a :Class; :comment "Generic type instance: List of integer"; :label "LIST_INT>"; :subClassOf kb:LIST . kb:LanguageAbilityMode a :Class; :label "LanguageAbilityMode"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "LanguageAbilityMode.ESGN"; :subClassOf kb:LanguageAbilityMode . a kb:CE; ; :label "LanguageAbilityMode.ESP"; :subClassOf kb:LanguageAbilityMode . a kb:CE; ; :label "LanguageAbilityMode.EWR"; :subClassOf kb:LanguageAbilityMode . a kb:CE; ; :label "LanguageAbilityMode.RSGN"; :subClassOf kb:LanguageAbilityMode . a kb:CE; ; :label "LanguageAbilityMode.RSP"; :subClassOf kb:LanguageAbilityMode . a kb:CE; ; :label "LanguageAbilityMode.RWR"; :subClassOf kb:LanguageAbilityMode . kb:LanguageAbilityProficiency a :Class; :label "LanguageAbilityProficiency"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "LanguageAbilityProficiency.E"; :subClassOf kb:LanguageAbilityProficiency . a kb:CE; ; :label "LanguageAbilityProficiency.F"; :subClassOf kb:LanguageAbilityProficiency . a kb:CE; ; :label "LanguageAbilityProficiency.G"; :subClassOf kb:LanguageAbilityProficiency . a kb:CE; ; :label "LanguageAbilityProficiency.P"; :subClassOf kb:LanguageAbilityProficiency . kb:Language_communication a :Class; :comment "Class reflects the language communication capabilities for an Entity, showing the languages with which the entity can communicate, the mode of communication (speak, read, write), the proficiency of that communication, and the Entity's preference."; :label "Language_communication"; :subClassOf kb:HL7RIM . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid274"; :domain kb:Language_communication; :label "Language_communication.communicates_with"; :range kb:Entity . a rdf:Property; a:maxCardinality "1"; :comment "A code indicating the language being communicated by the Entity (e.g. Spanish, Italian, German)."; :domain kb:Language_communication; :label "Language_communication.language_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; a:values , , , , , ; :comment "A code depicting the method of expression of the language (e.g. expressed spoken, expressed written, expressed signed, received spoken, received written, received sign)"; :domain kb:Language_communication; :label "Language_communication.mode_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment "An indication of whether or not the language is the one preferred by the entity for the indicated mode."; :domain kb:Language_communication; :label "Language_communication.preference_ind"; :range kb:BL . a rdf:Property; a:maxCardinality "1"; a:values , , , ; :comment "A code classifying the level of proficiency in the language (e.g. excellent, good, fair, poor)"; :domain kb:Language_communication; :label "Language_communication.proficiency_level_cd"; :range kb:CE . kb:Link_html a :Class; :comment "Link_html is based on the HTML anchor tag, and enables HTML-style hyperlinking semantics."; :label "Link_html"; :subClassOf kb:Context_structure . a rdf:Property; a:maxCardinality "1"; :comment "This attribute is part of the HTML anchor tag."; :domain kb:Link_html; :label "Link_html.href"; :range kb:ED . a rdf:Property; a:maxCardinality "1"; :comment "This attribute is part of the HTML anchor tag."; :domain kb:Link_html; :label "Link_html.name"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; a:values , , , , , , , , , , , , , , ; :comment "This attribute is part of the HTML anchor tag."; :domain kb:Link_html; :label "Link_html.rel"; :range . a rdf:Property; a:maxCardinality "1"; a:values , , , , , , , , , , , , , , ; :comment "This attribute is part of the HTML anchor tag."; :domain kb:Link_html; :label "Link_html.rev"; :range . a rdf:Property; a:maxCardinality "1"; :comment "This attribute is part of the HTML anchor tag."; :domain kb:Link_html; :label "Link_html.title"; :range kb:ST . kb:LivingArrangement a :Class; :label "LivingArrangement"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "LivingArrangement.G"; :subClassOf . a kb:CE; ; :label "LivingArrangement.H"; :subClassOf kb:LivingArrangement . a kb:CE; ; :label "LivingArrangement.I"; :subClassOf kb:LivingArrangement . a kb:CE; ; :label "LivingArrangement.M"; :subClassOf kb:LivingArrangement . a kb:CE; ; :label "LivingArrangement.N"; :subClassOf . a kb:CE; ; :label "LivingArrangement.R"; :subClassOf . a kb:CE; ; :label "LivingArrangement.T"; :subClassOf kb:LivingArrangement . a kb:CE; ; :label "LivingArrangement.X"; :subClassOf . kb:Living_subject a :Class; :comment "An organism or complex animal, alive or not. Instances of this class encompass mammals, birds, fishes, bacteria, parasites, fungi and viruses. Person is a specialization of this class."; :label "Living_subject"; :subClassOf kb:Entity . a rdf:Property; a:maxCardinality "1"; a:values , ; :comment """A code depicting the gender (sex) of a person (e.g., female, male). This code is used for administrative purposes. ExtRef: This information is reported on UB FL 15."""; :domain kb:Living_subject; :label "Living_subject.administrative_gender_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment "For newborn living subjects in a multiple birth, the order in which this living subject was born."; :domain kb:Living_subject; :label "Living_subject.birth_order_nbr"; :range kb:INT . a rdf:Property; a:maxCardinality "1"; :comment "The date and time of a living subject's birth or hatching."; :domain kb:Living_subject; :label "Living_subject.birth_time"; :range kb:TS . a rdf:Property; a:maxCardinality "1"; :comment "An indication that the subject is dead."; :domain kb:Living_subject; :label "Living_subject.deceased_ind"; :range kb:BL . a rdf:Property; a:maxCardinality "1"; :comment "The date and time that a living subject's death occurred."; :domain kb:Living_subject; :label "Living_subject.deceased_time"; :range kb:TS . a rdf:Property; a:maxCardinality "1"; :comment "A indication as to whether the living subject is part of a multiple birth."; :domain kb:Living_subject; :label "Living_subject.multiple_birth_ind"; :range kb:BL . a rdf:Property; a:maxCardinality "1"; :comment """An indication that the living subject is (as in "has donated" or "is willing to donate") an organ donor."""; :domain kb:Living_subject; :label "Living_subject.organ_donor_ind"; :range kb:BL . kb:LocalMarkupIgnore a :Class; :label "LocalMarkupIgnore"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "LocalMarkupIgnore.all"; :subClassOf kb:LocalMarkupIgnore . a kb:CS; ; :label "LocalMarkupIgnore.markup"; :subClassOf kb:LocalMarkupIgnore . kb:LocalRemoteControlStatus a :Class; :label "LocalRemoteControlStatus"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "LocalRemoteControlStatus.L"; :subClassOf kb:LocalRemoteControlStatus . a kb:CE; ; :label "LocalRemoteControlStatus.R"; :subClassOf kb:LocalRemoteControlStatus . kb:Local_attr a :Class; :comment "A component used to map local semantics into the exchange standard when local semantics have not yet been standardized."; :label "Local_attr"; :subClassOf kb:Context_structure . a rdf:Property; a:maxCardinality "1"; :comment "The name of the local attribute."; :domain kb:Local_attr; :label "Local_attr.name"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; :comment "The value of the local attribute."; :domain kb:Local_attr; :label "Local_attr.value"; :range kb:ST . kb:Local_markup a :Class; :comment "A component used to map local semantics into the exchange standard when local semantics have not yet been standardized."; :label "Local_markup"; :subClassOf kb:Context_structure . a rdf:Property; a:maxCardinality "1"; :comment "The descriptor attribute describes the element, and the value can be drawn from a local vocabulary domain."; :domain kb:Local_markup; :label "Local_markup.descriptor"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; a:values , ; :comment """The ignore attribute tells the receiver to ignore just the tag (ignore="markup"), or to ignore the tag and all contained content (ignore="all")."""; :domain kb:Local_markup; :label "Local_markup.ignore_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment "The render attribute indicates how the sender would render the contents. The value can be drawn from a local vocabulary domain."; :domain kb:Local_markup; :label "Local_markup.render"; :range kb:ST . kb:Logical_expression a :Class; :comment "http://protege.stanford.edu/kb#genid985"; :label "Logical_expression"; :subClassOf kb:Selection_expression . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid1033"; :domain kb:Logical_expression; :label "Logical_expression.has_left_side"; :range kb:Selection_expression . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid1037"; :domain kb:Logical_expression; :label "Logical_expression.has_right_side"; :range kb:Selection_expression . a rdf:Property; a:maxCardinality "1"; :comment "When more than one criteria is to be applied in the evaluation of candidate instances, a conjunction is supplied to identify how to relate an additional criteria. "; :domain kb:Logical_expression; :label "Logical_expression.relational_conjunction_cd"; :range kb:CS . kb:MDFAttributeType a :Class; :label "MDFAttributeType"; :subClassOf kb:HL7VocabularyConcept . kb:MDFSubjectAreaPrefix a :Class; :label "MDFSubjectAreaPrefix"; :subClassOf kb:HL7VocabularyConcept . kb:MO a :Class; :comment """A monetary amount is a quantity expressing the amount of money in some currency. Currencies are the units in which monetary amounts are denominated in different economic regions. While the monetary amount is a single kind of quantity (money) the exchange rates between the different units are variable. This is the principle difference between physical quantity and monetary amounts, and the reason why currency units are not physical units. Equality of two monetary amounts -- unlike physical quantities -- is determined as the joint equality of their value and currency properties independently. If the currencies are not equal, the amounts cannot be compared. Conversion between the currencies is outside the scope of this specification. In practice, foreign exchange rates are highly variable not only over long and short amounts of time, but also depending on location and access to currency trade markets."""; :label "MO"; :subClassOf kb:QTY . a rdf:Property; a:maxCardinality "1"; :comment "The currency unit as defined in ISO 4217."; :domain kb:MO; :label "MO.currency"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment """This is the magnitude of the monetary amount in terms of the currency unit. Note: monetary amounts are usually precise to 0.01 (one cent, penny, paisa, etc.) For large amounts, it is important not to store monetary amounts in floating point registers, since this may lose precision. However, this specification does not define the internal storage of real numbers as fixed or floating point numbers. The precision attribute of the real number type is the precision of the decimal representation, not the precision of the value. The real number type has no notion of uncertainty or accuracy. For example, "1.99 USD" (precision 3) times 7 is "13.93 USD" (precision 4) and should not be rounded to "13.9" to keep the precision constant."""; :domain kb:MO; :label "MO.value"; :range kb:REAL . kb:Managed_participation a :Class; :comment """A "stateful" participation. The primary example would be attending practitioner for an inpatient encounter. Rationale: The state attribute is being added to support attending physician participation on Encounters."""; :label "Managed_participation"; :subClassOf kb:Participation . a rdf:Property; a:maxCardinality "1"; :comment "A unique identifier for a participation."; :domain kb:Managed_participation; :label "Managed_participation.id"; :range . a rdf:Property; a:maxCardinality "1"; a:values , ; :comment "A code depicting the state of the participation (e.g., pending, active, complete, cancelled)."; :domain kb:Managed_participation; :label "Managed_participation.status_cd"; :range . kb:Manufactured_material a :Class; :comment "Things or combination of things transformed for a particular purpose by a non-natural or manufacturing process. This class encompasses containers, devices, software modules and facilities."; :label "Manufactured_material"; :subClassOf kb:Material . a rdf:Property; a:maxCardinality "1"; :comment "The date and time the manufacturer stops ensuring the safety, quality, and/or proper functioning of the material."; :domain kb:Manufactured_material; :label "Manufactured_material.expiration_time"; :range kb:TS . a rdf:Property; a:maxCardinality "1"; :comment "The lot number is a number used to identify a particular batch of manufactured material. It is usually printed on the label attached to the container holding the substance and on the packaging which houses the containerNote that a lot number is not meant to be a unique identifier, but is meaningful only when the product kind and manufacturer are also identified."; :domain kb:Manufactured_material; :label "Manufactured_material.lot_nm"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; :comment "Specifies the time at which the material is considered useable after it is activated (for instance through opening the bottle of a liquid.) If a kind of material is described (determiner_cd = KIND) only the width of that interval can be known, i.e., the duration after opening the reagent container at which the reagent substance is considered useable for its normal testing purpose. For an actual instance of the reagent (e.g., a specific bottle), the stability_time.low TS marks the time at which the reagent bottle has been opened (or the reagent was otherwise activated.) Together with the typical stability duration, this determines the stability_time.high TS beyond which the reagent is no longer considered useable for its normal testing purpose."; :domain kb:Manufactured_material; :label "Manufactured_material.stability_time"; :range . kb:MapRelationship a :Class; :label "MapRelationship"; :subClassOf kb:HL7VocabularyConcept . kb:MaritalStatus a :Class; :label "MaritalStatus"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "MaritalStatus.A"; :subClassOf kb:MaritalStatus . a kb:CE; ; :label "MaritalStatus.D"; :subClassOf kb:MaritalStatus . a kb:CE; ; :label "MaritalStatus.I"; :subClassOf kb:MaritalStatus . a kb:CE; ; :label "MaritalStatus.L"; :subClassOf kb:MaritalStatus . a kb:CE; ; :label "MaritalStatus.M"; :subClassOf kb:MaritalStatus . a kb:CE; ; :label "MaritalStatus.P"; :subClassOf kb:MaritalStatus . a kb:CE; ; :label "MaritalStatus.S"; :subClassOf kb:MaritalStatus . a kb:CE; ; :label "MaritalStatus.UB92"; :subClassOf kb:MaritalStatus . a kb:CE; ; :label "MaritalStatus.W"; :subClassOf kb:MaritalStatus . kb:MaritalStatusT a kb:CE; ; :label "MaritalStatusT"; :subClassOf kb:MaritalStatus . kb:Material a :Class; :comment "A Material is an Entity that excludes Living_subjects and places. Manufactured or processed products are considered material, even if they originate in living matter. Parts (e.g. organs) derived from living subjects are Material that may need to be tracked through associations with the individual Living_subject from which they were obtained. Examples of Material are pharmaceutical substances (including active vaccines containing retarded virus), disposable supplies, durable equipment, implantable devices, food items (including meat or plant products), waste, traded goods, etc."; :label "Material"; :subClassOf kb:Entity . a rdf:Property; a:maxCardinality "1"; :comment """This is a classifier describing the form of the material. This includes the typical state of matter (solid, liquid, gas) and, for therapeutic substances, the dose form. OpenIssue: Vocabulary domain should include, but is broader than, the DoseForm domain."""; :domain kb:Material; :label "Material.form_cd"; :range kb:CE . kb:MdfHmdMetSourceType a :Class; :label "MdfHmdMetSourceType"; :subClassOf kb:HL7VocabularyConcept . kb:MdfHmdRowType a :Class; :label "MdfHmdRowType"; :subClassOf kb:HL7VocabularyConcept . kb:MdfRmimRowType a :Class; :label "MdfRmimRowType"; :subClassOf kb:HL7VocabularyConcept . kb:MediaType a :Class; :label "MediaType"; :subClassOf kb:HL7VocabularyConcept . kb:Message a :Class; :comment "The Message class is the parent class of all HL7 Version 3 messages."; :label "Message"; :subClassOf kb:Transmission . a rdf:Property; a:maxCardinality "1"; :comment "The attribute identifies the conditions under which accept acknowledgements are required to be returned in response to this message. "; :domain kb:Message; :label "Message.accept_ack_cd"; :range kb:CS . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid1013"; :domain kb:Message; :label "Message.acknowledges"; :range kb:Acknowledgement . a rdf:Property; a:maxCardinality "1"; :comment "This attribute contains conditions under which application level acknowledgements are to be returned in response to this message. "; :domain kb:Message; :label "Message.application_ack_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment """Contains arbitrary attachments of data blocks to which can be referred to from the interior of the message. Any ITS is advised to represent the attachments behind the main message body. Attachments are referred to from the message body using the reference functionality of the ED data type. OpenIssue: Constrain the use of the ED data type in the attachment message type. Additionally, the appropriateness of this attribute in the Message class is being questioned. An alternative to consider would be the placement of this attribute in a new class maintaining a 0 to many relationship with the Message class."""; :domain kb:Message; :label "Message.attachment_txt"; :range kb:ED . a rdf:Property; a:maxCardinality "1"; :comment "The interaction identifier is a reference to the unique information interchange derived from the V3 MDF for specifying a message."; :domain kb:Message; :label "Message.interaction_id"; :range kb:II . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid1021"; :domain kb:Message; :label "Message.is_communicated_as"; :range kb:Control_event . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid1017"; :domain kb:Message; :label "Message.occurs_with"; :range kb:Acknowledgement . a rdf:Property; a:maxCardinality "1"; a:values , , ; :comment "This attribute defines whether the message is part of a production, training, or debugging system. "; :domain kb:Message; :label "Message.processing_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; a:values , , , ; :comment "This attribute defines whether the message is being sent in current processing, archive mode, initial load mode, restore from archive mode, etc."; :domain kb:Message; :label "Message.processing_mode_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment "The message profile identifier allows a given implementation to explicitly state how it varies from the standard message definition."; :domain kb:Message; :label "Message.profile_id"; :range . a rdf:Property; a:maxCardinality "1"; :comment "This attribute is provided for implementing the sequence number protocol. This field is incremented by one for each subsequent value assignment."; :domain kb:Message; :label "Message.sequence_nbr"; :range kb:INT . a rdf:Property; a:maxCardinality "1"; :comment "This attribute is matched by the receiving system to its own version to be sure the message will be interpreted correctly."; :domain kb:Message; :label "Message.version_id"; :range kb:ST . kb:MessageCondition a :Class; :label "MessageCondition"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "MessageCondition.0"; :subClassOf kb:MessageCondition . a kb:CE; ; :label "MessageCondition.100"; :subClassOf kb:MessageCondition . a kb:CE; ; :label "MessageCondition.101"; :subClassOf kb:MessageCondition . a kb:CE; ; :label "MessageCondition.102"; :subClassOf kb:MessageCondition . a kb:CE; ; :label "MessageCondition.103"; :subClassOf kb:MessageCondition . a kb:CE; ; :label "MessageCondition.200"; :subClassOf kb:MessageCondition . a kb:CE; ; :label "MessageCondition.201"; :subClassOf kb:MessageCondition . a kb:CE; ; :label "MessageCondition.202"; :subClassOf kb:MessageCondition . a kb:CE; ; :label "MessageCondition.203"; :subClassOf kb:MessageCondition . a kb:CE; ; :label "MessageCondition.204"; :subClassOf kb:MessageCondition . a kb:CE; ; :label "MessageCondition.205"; :subClassOf kb:MessageCondition . a kb:CE; ; :label "MessageCondition.206"; :subClassOf kb:MessageCondition . a kb:CE; ; :label "MessageCondition.207"; :subClassOf kb:MessageCondition . kb:ModifyIndicator a :Class; :label "ModifyIndicator"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "ModifyIndicator.M"; :subClassOf kb:ModifyIndicator . a kb:CS; ; :label "ModifyIndicator.N"; :subClassOf kb:ModifyIndicator . kb:NPPD a :Class; :comment """SET_UVP This is a generic data type to specify a value as a non-empty set of uncertain values forming a probability distribution (histogram.) All the elements in the set are considered alternatives and are rated each with its probability expressing the belief (or frequency) that each given value holds. The purpose of the non-parametric probability distribution is chiefly to support statistical data reporting as it occurs in measurements taken from many subjects and consolidated in a histogram. This occurs in epidemiology, veterinary medicine, laboratory medicine, but also in cost controlling and business process engineering. Semantically, the information of a stated value exists in contrast to the complement set of unstated possible values. Thus, semantically, a non-parametric probability distribution contains all possible values and assigns probabilities to each of them. ITS Note: even though semantically the NPPD assigns probabilities to all possible values, not all values need to be represented explicitly. Those possible values that are not mentioned in a NPPD data structure will have the rest-probability distributed equally over all unmentioned values. For example, if the value set is {A; B; C; D} but the NPPD value states just {(B; 0.5); (C; 0.25)} then the rest-probability is 1 - 0.75 = 0.25 which is distributed evenly over the complement set: {(A; 0.125); (D; 0.125)}. Semantically, the NPPD is the union of the stated probability distribution and the unstated complement with rest-probability distributed evenly. Just as with UVP, the type T is not formally constrained, even though there are reasonable and unreasonable use cases. Typically one would use the non-parametric probability distributions for unordered types, if only a "small" set of possible values is assigned explicit probabilities, or if the probability distribution can (or should) not be approximated with parametric methods. For other cases, one may prefer parametric probability distributions."""; :label "NPPD"; :subClassOf kb:SET . a rdf:Property; :label "NPPD.members"; :range kb:UVP . kb:Non_Person_living_subject a :Class; :comment "A non-human living subject.."; :label "Non_Person_living_subject"; :subClassOf kb:Living_subject . a rdf:Property; a:maxCardinality "1"; :comment "A code representing the breed of the living subject."; :domain kb:Non_Person_living_subject; :label "Non_Person_living_subject.breed_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment "An indication that the living subject was euthanized."; :domain kb:Non_Person_living_subject; :label "Non_Person_living_subject.euthanasia_ind"; :range kb:BL . a rdf:Property; a:maxCardinality "1"; a:values , ; :comment "A code indicating whether the reproductive organs of Non_person_living_subject have been surgically removed."; :domain kb:Non_Person_living_subject; :label "Non_Person_living_subject.gender_status_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment "A text string representing the genotypic or phenotypic strain of the living subject."; :domain kb:Non_Person_living_subject; :label "Non_Person_living_subject.strain_txt"; :range kb:ED . a rdf:Property; a:maxCardinality "1"; :comment "A code representing the taxonomy of the living subject."; :domain kb:Non_Person_living_subject; :label "Non_Person_living_subject.taxonomic_classification_cd"; :range kb:CE . kb:NullFlavor a :Class; :comment """A property can be of an exceptional value. Exceptional values express missing information and possibly the reason why the information is missing. Exceptional values are also called NULL-values, and the exception is called the "flavor" of NULL. Thus, every data value is either a proper value or it is NULL. If the value is NULL, the nullFlavor property is non-NULL. If the value is not NULL, its null flavor attribute is NULL (not applicable.) When a property, RIM attribute, or message field is called mandatory this means that any non-NULL value of the type to which the property belongs must have a non-NULL value for that property. In other HL7 specification the term "mandatory" is used while this specification formulates the mandatory con-straint explicitly."""; :label "NullFlavor"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "NullFlavour.ASKU"; :subClassOf . a kb:CS; ; :label "NullFlavour.NA"; :subClassOf . a kb:CS; ; :label "NullFlavour.NASK"; :subClassOf . a kb:CS; ; :label "NullFlavour.NAV"; :subClassOf . a kb:CS; ; :label "NullFlavour.NI"; :subClassOf kb:NullFlavor . a kb:CS; ; :label "NullFlavour.NINF"; :subClassOf . a kb:CS; ; :label "NullFlavour.NP"; :subClassOf . a kb:CS; ; :label "NullFlavour.OTH"; :subClassOf . a kb:CS; ; :label "NullFlavour.PINF"; :subClassOf . a kb:CS; ; :label "NullFlavour.UNK"; :subClassOf . kb:OID a :Class; :comment """The ISO Object Identifier is defined by ISO/IEC 8824:1990(E) clause 28. According to ISO/IEC 8824 an object identifier is a sequence of object identifier component values, which are integer numbers. These component values are ordered such that the root of the object identifier tree is the head of the list followed by all the arcs down to the leaf representing the information object identified by the OID. The demotion to LIST_INT> represents this path of object identifier component values from the root to the leaf. The value and namespace properties take the opposite view. The leaf (the last object identifier component value in the list) is considered the value property and the all the preceding object identifier component values except for the leaf are considered the namespace property. The namespace property is an OID by itself. The value/namespace view on ISO object identifiers has important semantic relevance. It represents the concepts of identifier value versus identifier assigning authority (namespace.)For Implementation Technologies that do not have native support for ISO OIDs, the ITS representations for OIDs may be a character string literal rather than a recursive data structure. The character string literal is more concise and most of the time OIDs will only be compared for equality but not analyzed further."""; :label "OID"; :subClassOf kb:ANY . a rdf:Property; a:maxCardinality "1"; :comment "all the preceding object identifier component values except for the leaf are considered the namespace property. The namespace property is an OID by itself."; :domain kb:OID; :label "OID.butleaf"; :range kb:OID . a rdf:Property; a:maxCardinality "1"; a:range "integer"; :comment "The leaf (the last object identifier component value in the list) is considered the value property "; :domain kb:OID; :label "OID.leaf"; :range :Literal . kb:ON a :Class; :comment """A name for an organization, such as "Health Level Seven, Inc." An organization name consists only of untyped name parts, prefixes, suffixes, and delimiters."""; :label "ON"; :subClassOf kb:EN . kb:Observation a :Class; :comment """Observations are actions performed in order to determine an answer or result value. Observation result values (Observation.value) include specific information about the observed object. The type and constraints of result values depend on the kind of action performed. Clinical documents commonly have 'Subjective' and 'Objective' findings, both of which are kinds of Observations. In addition, clinical documents commonly contain 'Assessments', which are also kinds of Observations. Thus, the establishment of a diagnosis is an Observation."""; :label "Observation"; :subClassOf kb:Act . a rdf:Property; a:maxCardinality "1"; :comment """Derived observations can be defined through association with other observations using relationships of derivation type (Act_relationship.type_cd = derivation.) For example, to define a derived observation for Mean Corpuscular Hemoglobin (MCH) one will associate the MCH observation with a Hemoglobin (HGB) observation (Act_relationship.sequence_nmb = 1) and a Red Blood cell Count (RBC) observation (Act_relationship.sequence_nmb = 2) Since MCH = HGB / RBC, the value of the derivation expression would be "$1 / $2". The derivation expression is a character string with a simple syntax similar to that of the UNIX "expr" utility, or the expression subset of the PERL or TCL language. All observations that are cited in the formula must be associated with the derived observation through links of type derivation with a unique Act_relationship.sequence_nmb. Such observation values are referred to by that sequence number preceded by a dollar sign ($). Defined operators are addition (+), subtraction (?), multiplication (*) and division (/). Parentheses can be used to overcome the usual precedence (left to right, multiplication before addition.) In addition to the basic arithmetic operations the usual mathematical functions are defined."""; :domain kb:Observation; :label "Observation.derivation_expr"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; a:values , , , ; :comment "This attribute allows for a very rough interpretation of the course or outcome of a service action. This is sometimes called \"abnormal flags\", however, the judgment of normalcy is just one of the common rough interpretations, and is often not relevant. For example, for the observation of a pathologic condition, it doesn�t make sense to state the normalcy, since pathologic conditions are never considered \"normal.\""; :domain kb:Observation; :label "Observation.interpretation_cd"; :range . a rdf:Property; a:maxCardinality "1"; a:values , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ; :comment "The method by which the result was achieved. This may be important to know when interpreting a report more thoroughly (e.g., blood pressure method: arterial puncture vs. Riva-Rocci, sitting vs. supine position, etc.) It should be noted that in some cases the method will already be specified by the Observation.type_cd and therefore does not need to be specified in Observation.method_cd."; :domain kb:Observation; :label "Observation.method_cd"; :range . a rdf:Property; a:maxCardinality "1"; a:values , ; :comment """The anatomical site or system that is the focus of the observation, if applicable. Most observation target sites are implied by the observation code and definition. For example, "heart murmur" always has the heart as target. This attribute is used when the observation target site needs to be refined, to distinguish right and left etc. If the subject of the Observation is something other than a human patient or animal, the attribute is used analogously to specify a structural landmark of the thing where the act focuses. For example, if the subject is a lake, the site could be inflow and outflow, etc. If the subject is a lymphatic node, "hilus," "periphery," etc. would still be valid target sites."""; :domain kb:Observation; :label "Observation.target_site_cd"; :range . a rdf:Property; a:maxCardinality "1"; :comment """The result value of an observation action. As was true with HL7 v2, this value can be of any data type. However, there are clearly more or less reasonable choices of data types as indicated below. Kind of observation :: Data type ::Notes (1) Quantitative measurements :: PQ ::Physical quantity (real number with unit.) This is the most usual choice. Note that numeric values must not be communicated as a simple character string (ST.) (2) Titer (e.g., 1:64) and other ratios (e.g. 1 out of 1000) :: RTO :: A ratio of two integer numbers (e.g., 1:128.) Sometimes by local conventions titers are reported as just the denominator (e.g., 32 instead of 1/32) Such conventions are confusing and should not be followed in HL7 messages. (3) Index (number without unit) :: REAL :: When a quantity does not have a proper unit, one can just send the number as a real number. Alternatively one can use a PQ with a dimensionless unit (e.g., 1 or %). An integer number should only be sent when the measurement is by definition an integer, which is an extremely rare case and then is most likely an ordinal (see below.) (4) Ranges (e.g., < 3; 12-20) :: IVL_PQ> :: Interval of physical quantity. Note that sometimes such intervals are used to report the uncertainty of measurement value. For uncertainty there are dedicated data type extensions available. (5) Ordinals (e.g., stage "IIa") :: CV, INT :: At this point, ordinals should be reported either as code values, (e.g., +, ++, +++; or I, IIa, IIb, III, IV) or as integers. In the future ordinals may be addressed by a separate data type. (6) Nominal results, "taxons" (e.g. organism type.) :: CD :: The Concept Descriptor (CD) is the most common data type to use for categorical results (e.g., diagnosis, complaint, color.) Such qualitative results are rarely simple Code Values (CV) if there is a tightly defined code system which everyone uses. (7) Image (still, movie) :: ED :: The encapsulated data type allows one to send an image (e.g., chest X-ray) or a movie (e.g., coronary angiography, cardiac echo.) (8) Waveform :: Waveforms can be sent using the waveform template developed by the Automated Data SIG for version 2.3. A mapping onto version 3 is shown farther below. In addition one can use the Encapsulated Data (ED) data type to send waveforms in other formats. (9) Formalized expressions :: ST :: The character string data type may exceptionally be used to convey formalized expressions that do not fit in any of the existing data types. However, use of the string data type is not allowed if the meaning can be represented by one of the existing data types. Note that many of the data types do have character string literal expressions too, so the field in the message can be formatted using character string literals and still have a distinct data type. OpenIssue: We should revisit the proper attribute to be used to transmit clinical documents."""; :domain kb:Observation; :label "Observation.value"; :range kb:ANY . kb:ObservationInterpretation a :Class; :label "ObservationInterpretation"; :subClassOf kb:HL7VocabularyConcept . a ; ; :label "ObservationInterpretation.<"; :subClassOf . a ; ; :label "ObservationInterpretation.>"; :subClassOf . a ; ; :label "ObservationInterpretation.B"; :subClassOf . a ; ; :label "ObservationInterpretation.Change"; :subClassOf kb:ObservationInterpretation . a ; ; :label "ObservationInterpretation.D"; :subClassOf . a ; ; :label "ObservationInterpretation.Exceptions"; :subClassOf kb:ObservationInterpretation . a ; ; :label "ObservationInterpretation.HH"; :subClassOf , . a ; ; :label "ObservationInterpretation.I"; :subClassOf . a ; ; :label "ObservationInterpretation.LL"; :subClassOf , . a ; ; :label "ObservationInterpretation.MS"; :subClassOf . a ; ; :label "ObservationInterpretation.N"; :subClassOf . a ; ; :label "ObservationInterpretation.Normality"; :subClassOf kb:ObservationInterpretation . a ; ; :label "ObservationInterpretation.NormalityAbnormal "; :subClassOf . a ; ; :label "ObservationInterpretation.NormalityAlert "; :subClassOf . a ; ; :label "ObservationInterpretation.NormalityHigh "; :subClassOf . a ; ; :label "ObservationInterpretation.NormalityLow "; :subClassOf . a ; ; :label "ObservationInterpretation.R"; :subClassOf . a ; ; :label "ObservationInterpretation.S"; :subClassOf . a ; ; :label "ObservationInterpretation.Susceptibility"; :subClassOf kb:ObservationInterpretation . a ; ; :label "ObservationInterpretation.U"; :subClassOf . a ; ; :label "ObservationInterpretation.VS"; :subClassOf . a ; ; :label "ObservationInterpretation.W"; :subClassOf . kb:ObservationMethod a :Class; :comment "I haven't included the codes from 0088 till 0270"; :label "ObservationMethod"; :subClassOf kb:HL7VocabularyConcept . a ; ; :label "ObservationMethod.0001"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0002"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0003"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0004"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0005"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0006"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0007"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0008"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0009"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0010"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0011"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0012"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0013"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0014"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0015"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0016"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0017"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0018"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0019"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0020"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0021"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0022"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0023"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0024"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0025"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0026"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0027"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0028"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0029"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0030"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0031"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0032"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0033"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0034"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0035"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0036"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0037"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0038"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0039"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0040"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0041"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0042"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0043"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0044"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0045"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0046"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0047"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0048"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0049"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0050"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0051"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0052"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0053"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0054"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0055"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0056"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0057"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0058"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0059"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0060"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0061"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0062"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0063"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0064"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0065"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0066"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0067"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0068"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0069"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0070"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0071"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0072"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0073"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0074"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0075"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0076"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0077"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0078"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0079"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0080"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0081"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0082"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0083"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0084"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0085"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0086"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0087"; :subClassOf kb:ObservationMethod . a ; ; :label "ObservationMethod.0271"; :subClassOf kb:ObservationMethod . kb:OrderableDrugForm a :Class; :label "OrderableDrugForm"; :subClassOf kb:HL7VocabularyConcept . kb:Organization a :Class; :comment "A formalized group of people with a common purpose (e.g. administrative, legal, political) and the infrastructure to carry out that purpose. Examples include companies and institutions, a government department, an incorporated body that is responsible for administering a facility, an insurance company."; :label "Organization"; :subClassOf kb:Entity . a rdf:Property; a:maxCardinality "1"; :comment "The postal and residential addresses of an organization."; :domain kb:Organization; :label "Organization.addr"; :range . a rdf:Property; a:maxCardinality "1"; :comment "The standard industry class code of the organization."; :domain kb:Organization; :label "Organization.standard_industry_class_cd"; :range kb:CE . kb:OrganizationNameType a :Class; :label "OrganizationNameType"; :subClassOf kb:HL7VocabularyConcept . kb:PIVL a :Class; :comment """The periodic interval of time specifies an interval of time that recurs periodically. Periodic intervals have two properties, phase and period. The phase specifies the interval prototype that is repeated every period. For example, "every eight hours for two minutes" is a periodic interval where the interval�s width equals two minutes and the period at which the interval recurs equals eight hours. The phase also marks the anchor point in time for the entire series of periodically recurring intervals. The recurrence of a periodic interval has no beginning or ending, but is infinite in both future and past. A periodic interval is fully specified when both the period and the phase are fully specified. The interval may be only partially specified where either only the width or only one boundary is specified. For example: "every eight hours for two minutes" specifies only the period and the phase�s width but no boundary of the phase. Conversely, "every eight hours starting at 4 o�clock" specifies only the period and the phase�s low boundary but not the phase�s high boundary. "Every eight hours for two minutes starting at 4 o�clock" is fully specified since the period, and both the phase�s low boundary and width are specified (low boundary and width implies the high boundary.) The periodic interval of time is a generic data type PIVL?T? where the type parameter T is restricted to the point in time (TS) data type and it�s extensions. The parametric probability distribution of point in time (PPD?TS?) is an extension of point in time and therefore can be used to form periodic intervals of probability distributions of point in time (PIVL?PPD?TS??) values (uncertain periodic interval.) Oftentimes repeating schedules are only approximately specified. For instance "three times a day for ten minutes each" does not usually mean a period of precisely 8 hours and does often not mean exactly 10 minutes intervals. Rather the distance between each occurrence may vary as much as between 3 and 12 hours and the width of the interval may be less than 5 minutes or more than 15 minutes. An uncertain periodic interval can be used to indicate how much leeway is allowed or how "timing-critical" the specification is."""; :label "PIVL"; :subClassOf . a rdf:Property; a:allowedClasses kb:CS, kb:IVL; a:maxCardinality "1"; a:values , ; :comment """A periodic interval may be specified aligned to the calendar underlying the phase. A non-aligned periodic interval recurs independent from the calendar. An aligned periodic interval is synchronized with the calendar. For example, "every 5th of the month" is a calendar aligned periodic interval. The period spans 28 to 31 days depending on the calendar month. Conversely, "every 30 days" is an independent period that will fall on a different date each month. The calendar alignment specifies a calendar cycle to which the periodic interval is aligned. The even flow of time will then be partitioned by the calendar cycle. The partitioning is called the calendar "grid" generated by the aligned-to calendar cycle. Each occurrence interval will then have equal distance from the earliest point in each partition. In other words, the distance from the next lower grid-line to the beginning of the interval is constant. For example, with "every 5th of the month" the alignment calendar cycle would be month of the year (MY.) The even flow of time is partitioned in months of the year. The distance between the beginning of each month and the beginning of its occurrence interval is 4 days (4 days because MY starts counting with 1.) Thus, as months differ in their number of days, the distances between the recurring intervals will vary slightly, so that the interval occurs always on the 5th."""; :domain kb:PIVL; :label "PIVL.alignment"; :range kb:ANY . a rdf:Property; a:maxCardinality "1"; a:minCardinality "1"; :comment "The period specifies how frequently the periodic interval recurs. The period is a physical quantity in the dimension of time (TS.diff.) For an uncertain periodic interval (PIVL_PPD) the period is a probability distribution over elapsed time (PPD). A non-NULL period exists for every non-NULL periodic interval."; :domain kb:PIVL; :label "PIVL.period"; :range kb:TS . a rdf:Property; a:maxCardinality "1"; :comment "The phase specifies the interval prototype that is repeated every period. The phase also marks the anchor point in time for the entire series of periodically recurring intervals. The recurrence of a periodic interval has no begin or end but is infinite in both future and past. A phase must be specified for every non-NULL periodic interval. The width of the phase must be less or equal the period."; :domain kb:PIVL; :label "PIVL.phase"; :range . kb:PN a :Class; :comment "Since most of the functionality of entity name is in support of person names, the person name (PN) is only a very minor restriction on the entity name. This restriction applies to the part qualifier."; :label "PN"; :subClassOf kb:EN . kb:PPD a :Class; :comment """A parametric probability distribution is a generic data type extension specifying an uncertain value of a quantity data type using a distribution function and its parameters. Aside from the specific parameters of the distribution, a mean (expected value) and standard deviation is always given to help maintain interoperability if receiving applications cannot deal with a certain probability distribution. Since a PPD extends the base type T, a simple T value is the mean (expected value or first moment) of the probability distribution. Applications that cannot deal with distributions will take the simple T value neglecting the uncertainty. That simple value of type T is also used to standardize the data for computing the distribution. Probability distributions are defined over integer or real numbers and normalized to a certain reference point (typically zero) and reference unit (e.g., standard deviation = 1). When other quantities defined in this specification are used as base types, the mean and the standard deviation are used to scale the probability distribution. For example, if a PPD for a length is given with mean 20 ft and a standard deviation of 2 in, the normalized distribution function f(x) that maps a real number x to a probability would be translated to f�(x�) that maps a length x� to a probability as f�(x�) = f((x�? ? ) / ?). Where applicable, the PPD specification conforms to the ISO Guide to the Expression of Uncertainty in Measurement (GUM) as reflected by NIST Technical Note 1297, Guidelines for Evaluating and Expressing the Uncertainty of NIST Measurement Results. The PPD specification does not describe how uncertainty is to be evaluated but only how it is expressed. The concept of "standard uncertainty" as set forth by the ISO GUM corresponds to the "standard deviation" property of the PPD."""; :label "PPD"; :subClassOf kb:T . a rdf:Property; a:maxCardinality "1"; :comment "The standard deviation of the probability distribution. The standard deviation is used to normalize the data for computing the distribution function. Applications that can not deal with probability distributions can still get an idea about the confidence level by looking at the standard deviation.\n\nThe standard deviation of a probability distribution over a type T is of a related type that can express differences between values of type T. If T is REAL or INT, T.diff is also REAL or INT respectively. However if T is a point in time (TS), T.diff is a physical quantity (PQ) in the dimension of time.\n\nThe standard deviation is what ISO GUM calls \"standard uncertainty.\""; :domain kb:PPD; :label "PPD.standardDeviation"; :range kb:T . a rdf:Property; a:maxCardinality "1"; a:values , , , , , , , , ; :comment """This code specifies the type of probability distribution. Possible values are as shown in the attached table. The NULL value (unknown) for the type code indicates that the probability distribution type is unknown. In that case, the standard deviation has the meaning of an informal guess. Many distribution types are usually defined in terms of special parameters (e.g., the parameters alpha and beta for the gamma-distribution, number of degrees of freedom for the t-distribution, etc.) For all distribution types, however, the mean and standard deviation are defined. The PPD data type is specified with the parameters mean and standard distribution only. ITS Note: an ITS does not need to represent any of the specialized parameters for the distribution types. As it turns out, all of these specialized parameters can be calculated from the mean and standard deviation. The three distribution-types unknown (NULL), uniform and normal must be supported by every system that claims to support PPD. All other distribution types are optional. When a system interpreting a PPD representation encounters an unknown distribution type, it maps this type to the unknown (NULL) distribution-type."""; :domain kb:PPD; :label "PPD.type"; :range kb:CV . kb:PQ a :Class; :comment """A physical quantity is a dimensioned quantity expressing the result of a measurement act and are represented as pairs of value and unit. However, semantically, a physical quantity is more than a pair of value and unit. To find out whether two physical quantities are equal, it is not enough to compare equality of their two values and units independently. For example, semantically 100 cm equals 1 m although neither values nor units are equal. To define equality we introduce the notion of a canonical form. Every physical quantity has a canonical form. The canonical form is a physical quantity expressed as a pair of value and unit such that each dimension in a given unit system has one and only one canonical value-unit pair. Defining the canonical form is not subject of this specification, only asserting that such a canonical form exists for every physical quantity. A physical quantity is equal to its canonical form. For example, for a unit system based on the Syst�me International (SI) one can define the canonical form as (a) the product of only the base units; (b) without prefixes; where (c) only multiplication and exponents are used (no division operation); and (d) where the seven base units appear in a defined ordering (e.g., m, s, g, ...) Thus, 1 mm Hg would be expressed as 133322 m-1.s-2.g. As can be seen, the rules how to build the canonical form of units may be quite complex. However, for the semantic specification it doesn�t matter how the canonical form is built, nor what specific canonical form is chosen, only that some canonical form could be defined. Two physical quantities are equal if each their values and their units of their canonical forms are equal. Two physical quantities compare each other (and have an ordering and difference) if the units of their canonical forms are equal."""; :label "PQ"; :subClassOf kb:QTY . a rdf:Property; a:maxCardinality "1"; :comment """This is the unit of measure. Note that equality of physical quantity does not require the values and units to be equal independently. Value and unit is only how we represent physical quantities. For example, 1 m equals 100 cm. Although the units are different and the values are different, the physical quantities are equal! Therefore one should never expect a particular unit for a physical quantity but instead provide automated conversion between different comparable units."""; :domain kb:PQ; :label "PQ.unit"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment "This is the magnitude of the quantity measured in terms of the unit."; :domain kb:PQ; :label "PQ.value"; :range kb:REAL . kb:Parameter a :Class; :comment "The Parmeter class is an implementation class that represents the structure of parameters that may be specified with the Query-by-parameter mechanisms of the V3 query framework. Parameters may be set of name/value pairs, a named parameter list with a set of name/value pairs or any combination the previous two options."; :label "Parameter"; :subClassOf kb:HL7RIM . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid1027"; :domain kb:Parameter; :label "Parameter.has"; :range kb:Query_by_parameter . a rdf:Property; a:maxCardinality "1"; :comment "The Parameter.id can assist in tracing problems with implementing the query-by-parameter mechanism. "; :domain kb:Parameter; :label "Parameter.id"; :range kb:II . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid1045"; :domain kb:Parameter; :label "Parameter.may_contain"; :range kb:Parameter_list . a rdf:Property; a:maxCardinality "1"; :comment """In a Parameter_list, specifies a named list of parameters (name/value pairs) that is referenced in a query conformance statement. In A_parameter, identifies the name of the element field in an HMD specified for query response."""; :domain kb:Parameter; :label "Parameter.nm"; :range kb:ST . kb:Parameter_item a :Class; :comment "Represents a valued element structure for the element specified in the query response."; :label "Parameter_item"; :subClassOf kb:Parameter . a rdf:Property; a:maxCardinality "1"; :comment "The Parameter_item.type_cd attribute provides a unique identification to an element within a specified query response structure."; :domain kb:Parameter_item; :label "Parameter_item.semantics_txt"; :range kb:ST . a rdf:Property; a:maxCardinality "1"; :comment "Represents a valued element structure for the element specified in the query response."; :domain kb:Parameter_item; :label "Parameter_item.value"; :range kb:ANY . kb:Parameter_list a :Class; :comment "Specifies a named list of parameters (name/value pairs) that is referenced in a query conformance statement."; :label "Parameter_list"; :subClassOf kb:Parameter . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid1043"; :domain kb:Parameter_list; :label "Parameter_list.is_part_of"; :range kb:Parameter . kb:ParameterizedDataType a :Class; :label "ParameterizedDataType"; :subClassOf kb:HL7VocabularyConcept . kb:Participation a :Class; :comment """An association between a Role and an Act. The Participation represents the involvement of the Entity playing the Role with regard to the associated Act. A single Role may participate in multiple Acts and a single Act may have multiple participating Roles. A single Participation is always an association between a particular Role and a particular Act. Participation is limited to the scope of the Act, as opposed to Role, which defines the competency of an Entity irrespective of any Act. Participations are generally grouped into actors and targets. Examples of actors are nurses, doctors, family members, notary publics, and service organizations -- every person or organization that is capable of independent decisions and can thus be responsible (and liable) for the actions performed. Target participants in an act may include the patient, the patient's spouse, family, or community, a specimen drawn from the patient or from any object of interest. Actors can participate in an action in different ways. For example, primary surgeon, assistant surgeon, sterile nurse, and nurse assistant are all actors in a surgical procedure, who are more or less immediately involved in the action. However, payers, supervisors, provider organizations (e.g., "MicroLab") and their delegates may be actors too, even though they might not be individual persons who have their "hands on" the action. The notion of multiple actors with specific functions touches and partially overlaps on two "sides" with related concepts of the RIM, and understanding the distinctions is important to use the RIM constructs correctly. On the one "side" actor functions look similar to Roles (e.g., healthcare practitioner, guarantor, contact-person,) and capability and certification (e.g., certified surgeon vs. resident, certified nurse midwife vs. other midwife practitioner, registered nurse vs. other nurse practitioner.) The professional credentials of a person may be quite different from what a person actually does. The most common example is interns and residents performing anesthesia or surgeries under (more or less) supervision of attending specialists. The opposite example is people who are both medical doctors and registered nurses and who perform the function of a nurse. Thus, Roles and certification refer to the static capabilities of a person (person-related) while participating actors refer to the particular function an actor played in the activity. On the other "side" the actor concept interferes with sub-activities. Whenever multiple actors are involved in an act, each actor performs a different task (with the extremely rare exception of such symmetrical activities as two people pulling a rope from either end.) Thus, the presence of multiple actors could be equally well modeled as an act consisting of sub-acts where each act would have only one performing actor For example, a record of a surgical service may include the actors of type: (a) consenter, (b) primary surgeon, and (c) anesthetist. These three actors really perform different tasks, which can be represented as three related acts: (a) the consent, (b) the surgery proper, and (c) the anesthesia act in parallel to the surgery. If we used the sub-acts, the consenter, surgeon and anesthetist could simply be of actor type "performer." Thus the more sub-acts we use, the fewer different actor types need to be distinguished, and the fewer sub-acts we use, the more distinct actor types we need. Note that the perception of a task as "atomic" or "composite" (of sub-tasks) depends on local business rules and may differ from department to department. In principle, every task can be thought of as being a composite of sub-tasks. We thus say that actions are "fractal." The paradigmatic example of the fractal nature of activities is a "robotic arm" doing some simple action as reaching for a tool in front of it. The seemingly simple activity of the robotic arm decomposes into complex control and coordination procedures and movements, action of separate motors and switches, etc. (We sometimes use the key-phrase "robotic arm discussion" to recall the fractal nature of actions, since this example has been brought up over and over again, independently by different people.) As a rule of thumb, sub-tasks should be considered instead of multiple actors when each sub-task requires special scheduling, or billing, or if overall responsibilities for the sub-tasks are different. In most cases, however, human resources are scheduled by teams (instead of individuals,) billing tends to lump many sub-tasks together into one position, and overall responsibility often rests with one attending physician, chief nurse, or head of department. This model allows both the multi-actor and the muli-act approach to represent the business reality, with a slight bias towards "lumping" minor sub-activities into the overall act."""; :label "Participation"; :subClassOf kb:HL7RIM . a rdf:Property; a:maxCardinality "1"; a:values , , , , , ; :comment """A code specifying the extent to which the Entity playing the participating Role, usually as a target Participation, is aware of the associated Act, and especially of the observation made. For example, a patient (or his next family members) may not be aware of a malignancy diagnosis, the patient and family may be aware at different times, and some patients may go through a phase of denial."""; :domain kb:Participation; :label "Participation.awareness_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment "Specifies if this participation can be inherited along conductive act-relationships."; :domain kb:Participation; :label "Participation.context_control_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; a:values , , , , , , , , , , , , , ; :comment """A code specifying the function played by the Participation in the Act. The code can accommodate the huge variety and nuances of functions that Participants may perform in the act. The number and kinds of functions applicable depends on the special kind of act. E.g., each operation and method may require a different number of assistant surgeons or nurses."""; :domain kb:Participation; :label "Participation.function_cd"; :range kb:CD . a rdf:Property; a:inverseProperty ; a:maxCardinality "1"; :comment "http://protege.stanford.edu/kb#genid498"; :domain kb:Participation; :label "Participation.has"; :range kb:Act . a rdf:Property; a:maxCardinality "1"; a:values , , , , ; :comment """A code specifying the modality by which the Entity playing the Role is participating in the Act. Examples include physically present, over the telephone, or in written communication. Particularly for author (originator) participants this is used to specify whether the information represented by the act was initially provided verbally, (hand)written, or electronically."""; :domain kb:Participation; :label "Participation.mode_cd"; :range kb:CE . a rdf:Property; a:maxCardinality "1"; :comment "A textual or multimedia depiction of commentary related to Participation."; :domain kb:Participation; :label "Participation.note_txt"; :range kb:ED . a rdf:Property; a:inverseProperty ; :comment "http://protege.stanford.edu/kb#genid94"; :domain kb:Participation; :label "Participation.participates_in"; :range kb:Role . a rdf:Property; a:maxCardinality "1"; :comment """An integer specifying the relative order of the Participation in relation to other Participations having the same associated Act. The sequencing might be undertaken for functional reasons or to establish a priority between participations. One example is the sequencing of covered party participations to establish a coordination of benefits sequence in insurance claims."""; :domain kb:Participation; :label "Participation.sequence_nbr"; :range kb:INT . a rdf:Property; a:maxCardinality "1"; a:values , , ; :comment """A code specifying circumstances related to the requirements for and the existence of a signature of the Entity playing the Role associated with the Participation. For example, a surgical Procedure act object (representing a procedure report) requires a signature of the performing and responsible surgeon, and possibly other participants. See also: Participation.signature_txt."""; :domain kb:Participation; :label "Participation.signature_cd"; :range kb:CS . a rdf:Property; a:maxCardinality "1"; :comment """A textual or multimedia depiction of the signature by which the Entity playing the Role associated with the Participation endorses that its participation in the Act is as stated in the Participation.type_cd; indicating that it assumes the associated accountability for the Act. For example, an AUTHOR assumes accountability for the truth of the Act statement to the best of his knowledge, whereas an information RECIPIENT would only sign the fact that he has received the information. The signature can be represented in many different ways either inline or by reference according to the ED data type. Typical cases are: 1) Paper-based signatures: the ED data type may refer to some document or file that can be retrieved through an electronic interface to a hardcopy archive. 2) Electronic signature: this attribute can represent virtually any electronic signature scheme. 3) Digital signature: in particular, this attribute can represent digital signatures, for example, by reference to a signature data block that is constructed in accordance to a digital signature standard, such as XML-DSIG, PKCS#7, PGP, etc."""; :domain kb:Participation; :label "Participation.signature_txt"; :range kb:ED . a rdf:Property; a:maxCardinality "1"; :comment "An interval of time specifying the effective period of the Participation."; :domain kb:Participation; :label "Participation.time"; :range . a rdf:Property; a:maxCardinality "1"; a:values , ; :comment """A code depicting the kind of Participation or involvement the Entity playing the Role associated with the Participation has with regard to the associated Act. The number and kinds of involved participants also depend on the special kind of act. The "ParticipationType" vocabulary domain defines a few orthogonal axes along which Participation types can be defined more regularly. For example, one axis represents the physical performance of the action; another axis represents the responsibility for the action, yet another represents authoring the information in the Act object. A Participant can have one or more of these types to a certain degree. However, the business semantics of these types is too variant to be mathematically analyzed. For this reason, we split the coding of the kind of Participant's involvement into two attributes. The Participant.type_cd contains only categories that have crisp semantic relevance in the scope of HL7. It is a coded attribute without exceptions and no alternative coding systems allowed. Conversely, the Participation.function_cd is a mostly locally defined descriptor for the kind of professional activity carried out by the participant."""; :domain kb:Participation; :label "Participation.type_cd"; :range kb:CS . kb:ParticipationFunction a :Class; :label "ParticipationFunction"; :subClassOf kb:HL7VocabularyConcept . a kb:CD; ; :label "ParticipationFunction.ADMPHYS"; :subClassOf kb:ParticipationFunction . a kb:CD; ; :label "ParticipationFunction.ANEST"; :subClassOf kb:ParticipationFunction . a kb:CD; ; :label "ParticipationFunction.ANRS"; :subClassOf kb:ParticipationFunction . a kb:CD; ; :label "ParticipationFunction.ATTPHYS"; :subClassOf kb:ParticipationFunction . a kb:CD; ; :label "ParticipationFunction.DISPHYS"; :subClassOf kb:ParticipationFunction . a kb:CD; ; :label "ParticipationFunction.FASST"; :subClassOf kb:ParticipationFunction . a kb:CD; ; :label "ParticipationFunction.MDWF"; :subClassOf kb:ParticipationFunction . a kb:CD; ; :label "ParticipationFunction.NASST"; :subClassOf kb:ParticipationFunction . a kb:CD; ; :label "ParticipationFunction.PCP"; :subClassOf kb:ParticipationFunction . a kb:CD; ; :label "ParticipationFunction.PRISURG"; :subClassOf kb:ParticipationFunction . a kb:CD; ; :label "ParticipationFunction.RNDPHYS"; :subClassOf kb:ParticipationFunction . a kb:CD; ; :label "ParticipationFunction.SASST"; :subClassOf kb:ParticipationFunction . a kb:CD; ; :label "ParticipationFunction.SNRS"; :subClassOf kb:ParticipationFunction . a kb:CD; ; :label "ParticipationFunction.TASST"; :subClassOf kb:ParticipationFunction . kb:ParticipationMode a :Class; :label "ParticipationMode"; :subClassOf kb:HL7VocabularyConcept . a kb:CE; ; :label "ParticipationMode.DICTATE"; :subClassOf . a kb:CE; ; :label "ParticipationMode.EMAILWRIT"; :subClassOf . a kb:CE; ; :label "ParticipationMode.ElectronicData "; :subClassOf kb:ParticipationMode . a kb:CE; ; :label "ParticipationMode.FACE"; :subClassOf . a kb:CE; ; :label "ParticipationMode.FAXWRIT"; :subClassOf . a kb:CE; ; :label "ParticipationMode.HANDWRIT"; :subClassOf . a kb:CE; ; :label "ParticipationMode.PHONE"; :subClassOf . a kb:CE; ; :label "ParticipationMode.PHYSICAL"; :subClassOf kb:ParticipationMode . a kb:CE; ; :label "ParticipationMode.REMOTE"; :subClassOf kb:ParticipationMode . a kb:CE; ; :label "ParticipationMode.TYPEWRIT"; :subClassOf . a kb:CE; ; :label "ParticipationMode.VIDEOCONF"; :subClassOf . a kb:CE; ; :label "ParticipationMode.Verbal "; :subClassOf kb:ParticipationMode . a kb:CE; ; :label "ParticipationMode.Written "; :subClassOf kb:ParticipationMode . kb:ParticipationSignature a :Class; :label "ParticipationSignature"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "ParticipationSignature.I"; :subClassOf kb:ParticipationSignature . a kb:CS; ; :label "ParticipationSignature.S"; :subClassOf kb:ParticipationSignature . a kb:CS; ; :label "ParticipationSignature.X"; :subClassOf kb:ParticipationSignature . kb:ParticipationStatus a :Class; :label "ParticipationStatus"; :subClassOf kb:HL7VocabularyConcept . a ; ; :label "ParticipationStatus.NormalParticipationStatus "; :subClassOf kb:ParticipationStatus . a ; ; :label "ParticipationStatus.active"; :subClassOf . a ; ; :label "ParticipationStatus.cancelled"; :subClassOf . a ; ; :label "ParticipationStatus.completed"; :subClassOf . a ; ; :label "ParticipationStatus.nullified"; :subClassOf kb:ParticipationStatus . a ; ; :label "ParticipationStatus.pending"; :subClassOf . kb:ParticipationType a :Class; :label "ParticipationType"; :subClassOf kb:HL7VocabularyConcept . a kb:CS; ; :label "ParticipationType.ASS"; :subClassOf . a kb:CS; ; :label "ParticipationType.ATTN"; :subClassOf . a kb:CS; ; :label "ParticipationType.AUT"; :subClassOf . a kb:CS; ; :label "ParticipationType.ActorSignatories"; :subClassOf . a kb:CS; ; :label "ParticipationType.BEN"; :subClassOf . a kb:CS; ; :label "ParticipationType.CBC"; :subClassOf . a kb:CS; ; :label "ParticipationType.CNS"; :subClassOf . a kb:CS; ; :label "ParticipationType.CON"; :subClassOf . a kb:CS; ; :label "ParticipationType.COV"; :subClassOf . a kb:CS; ; :label "ParticipationType.CST"; :subClassOf . a kb:CS; ; :label "ParticipationType.ENT"; :subClassOf . a kb:CS; ; :label "ParticipationType.ESC"; :subClassOf . a kb:CS; ; :label "ParticipationType.INF"; :subClassOf . a kb:CS; ; :label "ParticipationType.InformationGenerator"; :subClassOf . a kb:CS; ; :label "ParticipationType.InformationRecipients"; :subClassOf . a kb:CS; ; :label "ParticipationType.PRF"; :subClassOf . a kb:CS; ; :label "ParticipationType.PhysicalPerformer"; :subClassOf . a kb:CS; ; :label "ParticipationType.REF"; :subClassOf . a kb:CS; ; :label "ParticipationType.RESPROV"; :subClassOf . a kb:CS; ; :label "ParticipationType.REV"; :subClassOf . a kb:CS; ; :label "ParticipationType.SPV"; :subClassOf . a kb:CS; ; :label "ParticipationType.ServiceActor "; :subClassOf kb:ParticipationType . a kb:C