URL,Version,Status,OIDs,Name,Title,Description,Used
http://dicom.nema.org/resources/ontology/DCM,01,active,"1.2.840.10008.2.16.4",DICOM Controlled Terminology Definitions,,"DICOM Code Definitions (Coding Scheme Designator ""DCM"" Coding Scheme Version ""01"")","ValueSet/participation-role-type,ValueSet/dicm-405-mediatype,ValueSet/audit-event-sub-type,ValueSet/audit-event-type,ValueSet/security-role-type"
http://hl7.org/fhir/administrative-gender,4.0.1,active,"2.16.840.1.113883.4.642.4.2",AdministrativeGender,AdministrativeGender,"The gender of a person used for administrative purposes.","ValueSet/administrative-gender"
http://hl7.org/fhir/audit-event-action,4.0.1,draft,"2.16.840.1.113883.4.642.4.453",AuditEventAction,AuditEventAction,"Indicator for type of action performed during the event that generated the event.","ValueSet/audit-event-action"
http://hl7.org/fhir/audit-event-outcome,4.0.1,draft,"2.16.840.1.113883.4.642.4.455",AuditEventOutcome,AuditEventOutcome,"Indicates whether the event succeeded or failed.","ValueSet/audit-event-outcome"
http://hl7.org/fhir/identifier-use,4.0.1,active,"2.16.840.1.113883.4.642.4.58",IdentifierUse,IdentifierUse,"Identifies the purpose for this identifier, if known .","ValueSet/identifier-use"
http://hl7.org/fhir/link-type,4.0.1,active,"2.16.840.1.113883.4.642.4.424",LinkType,LinkType,"The type of link between this patient resource and another patient resource.","ValueSet/link-type"
http://hl7.org/fhir/network-type,4.0.1,draft,"2.16.840.1.113883.4.642.4.457",AuditEventAgentNetworkType,AuditEventAgentNetworkType,"The type of network access point of this agent in the audit event.","ValueSet/network-type"
http://hl7.org/fhir/resource-types,4.0.1,active,,ResourceType,ResourceType,"One of the resource types defined as part of this version of FHIR.","ValueSet/audit-entity-type,ValueSet/resource-types"
http://hl7.org/fhir/restful-interaction,4.0.1,active,,FHIR Restful Interactions,,"The set of interactions defined by the RESTful part of the FHIR specification.","ValueSet/audit-event-sub-type,ValueSet/AllUpdateVS,ValueSet/AllSearchVS"
http://terminology.hl7.org/CodeSystem/audit-entity-type,1.0.1,active,"2.16.840.1.113883.4.642.1.1134",AuditEventEntityType,Audit event entity type,"Code for the entity type involved in the audit event.","ValueSet/audit-entity-type"
http://terminology.hl7.org/CodeSystem/audit-event-type,1.0.0,active,"2.16.840.1.113883.4.642.1.1136",AuditEventID,Audit Event ID,"Event Types for Audit Events - defined by DICOM with some FHIR specific additions.","ValueSet/audit-event-type"
http://terminology.hl7.org/CodeSystem/contractsignertypecodes,1.0.1,active,"2.16.840.1.113883.4.642.1.1201",ContractSignerTypeCodes,Contract Signer Type Codes,"This value set includes sample Contract Signer Type codes.","ValueSet/participation-role-type,ValueSet/security-role-type"
http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle,2.0.0,active,,DicomAuditMessageRecordLifecycleEvents,DICOM Audit Message Record Lifecycle Events,"Attached is vocabulary for the record lifecycle events, as per DICOM Audit Message, ","ValueSet/object-lifecycle-events"
http://terminology.hl7.org/CodeSystem/extra-security-role-type,1.0.1,active,,SecurityRoleType,Security Role Type,"This CodeSystem contains Additional FHIR-defined Security Role types not defined elsewhere","ValueSet/participation-role-type,ValueSet/security-role-type"
http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle,1.0.0,active,,Iso_21089_2017_Health_Record_Lifecycle_Events,ISO 21089 2017 Health Record Lifecycle Events,"Attached is vocabulary for the 27 record lifecycle events, as per ISO TS 21089-2017, Health Informatics - Trusted End-to-End Information Flows, Section 3, Terms and Definitions (2017, at ISO Central Secretariat, passed ballot and ready for publication).  This will also be included in the FHIR EHR Record Lifecycle Event Implementation Guide, balloted and (to be) published with FHIR STU-3.","ValueSet/audit-event-type,ValueSet/object-lifecycle-events"
http://terminology.hl7.org/CodeSystem/object-role,1.1.0,active,"2.16.840.1.113883.4.642.1.1135",AuditEventEntityRole,AuditEventEntityRole,"Code representing the role the entity played in the audit event.","ValueSet/RestObjectRoles,ValueSet/object-role"
http://terminology.hl7.org/CodeSystem/security-source-type,1.0.0,active,"2.16.840.1.113883.4.642.1.1137",AuditEventSourceType,Audit Event Source Type,"The type of process where the audit event originated from.","ValueSet/audit-source-type"
http://terminology.hl7.org/CodeSystem/v2-0131,2.0.0,active,"2.16.840.1.113883.18.58",ContactRole2,contactRole2,"Code system of concepts which specify a relationship role that the next of kin/associated parties plays with regard to the patient. Also used in referrals, for example, it may be necessary to identify the contact representative at the clinic that sent a referral. Used in HL7 Version 2 messaging in the NK1 and CTD segments after 2.5, when it replace 2.16.840.1.113883.18.57.","ValueSet/patient-contactrelationship"
http://terminology.hl7.org/CodeSystem/v2-0203,5.0.0,active,"2.16.840.1.113883.18.108",IdentifierType,identifierType,"HL7-defined code system of concepts specifying type of identifier. Used in HL7 Version 2.x messaging data types CX, PLN, PPN, XCN and XON.","ValueSet/identifier-type"
http://terminology.hl7.org/CodeSystem/v3-ActReason,3.1.0,active,"2.16.840.1.113883.5.8",ActReason,ActReason,"A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type ""has reason"" linking to another Act.    *Examples:* Example reasons that might qualify for being coded in this field might be: ""routine requirement"", ""infectious disease reporting requirement"", ""on patient request"", ""required by law"".","ValueSet/v3-PurposeOfUse"
http://terminology.hl7.org/CodeSystem/v3-MaritalStatus,3.0.0,active,"2.16.840.1.113883.5.2",MaritalStatus,MaritalStatus,"\* \* \* No description supplied \* \* \*    *Open Issue:* The specific meanings of these codes can vary somewhat by jurisdiction and implementation so caution should be used when determining equivalency.    *Open Issue:* fixing and completion of the hierarchy and proper good definitions of all the concepts is badly needed.","ValueSet/marital-status"
http://terminology.hl7.org/CodeSystem/v3-NullFlavor,3.0.0,active,"2.16.840.1.113883.5.1008",NullFlavor,NullFlavor,"A collection of codes specifying why a valid value is not present.","ValueSet/marital-status"
http://terminology.hl7.org/CodeSystem/v3-ParticipationFunction,3.0.0,active,"2.16.840.1.113883.5.88",ParticipationFunction,ParticipationFunction,"This code is used to specify the exact function an actor had in a service in all necessary detail. This domain may include local extensions (CWE).","ValueSet/participation-role-type,ValueSet/security-role-type"
http://terminology.hl7.org/CodeSystem/v3-ParticipationType,5.0.0,active,"2.16.840.1.113883.5.90",ParticipationType,ParticipationType,"A code specifying the meaning and purpose of every Participation instance. Each of its values implies specific constraints on the Roles undertaking the participation.","ValueSet/participation-role-type,ValueSet/DataSources,ValueSet/security-role-type"
http://terminology.hl7.org/CodeSystem/v3-RoleClass,4.0.0,active,"2.16.840.1.113883.5.110",RoleClass,RoleClass,"Codes for the Role class hierarchy. The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role. Roles names are derived from the name of the playing entity in that role.    The role hierarchy stems from three core concepts, or abstract domains:     *  **RoleClassOntological** is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity.   *  **RoleClassPartitive** collects roles in which the playing entity is in some sense a ""part"" of the scoping entity.   *  **RoleClassAssociative** collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between:             *  **RoleClassPassive** which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity.       *  **RoleClassMutualRelationship** which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may be *de facto* behavior. Thus, this sub-domain is further divided into:                     *  **RoleClassRelationshipFormal** in which the relationship is formally defined, frequently by a contract or agreement.           *  **Personal relationship** which inks two people in a personal relationship.    The hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the ""Personal relationship"" which is a leaf concept.    *OpenIssue:* Description copied from Concept Domain of same name. Must be verified.","ValueSet/participation-role-type,ValueSet/security-role-type"
http://terminology.hl7.org/CodeSystem/v3-RoleCode,3.0.0,active,"2.16.840.1.113883.5.111",RoleCode,RoleCode,"A set of codes further specifying the kind of Role; specific classification codes for further qualifying RoleClass codes.","ValueSet/participation-role-type,ValueSet/security-role-type"
urn:ietf:bcp:47,2.0.1,active,"2.16.840.1.113883.6.121",Ietf3066,Tags for the Identification of Languages,"Older value from OID registry.  Superceded; see recommendations in BCP-47.","ValueSet/languages"
