@medplum/definitions

{ "resourceType" : "Bundle", "id" : "v3-valuesets", "meta" : { "lastUpdated" : "2019-11-01T09:29:23.356+11:00" }, "type" : "collection", "entry" : [{ "fullUrl" : "http://hl7.org/fhir/ValueSet/v3-MessageWaitingPriority", "resource" : { "resourceType" : "ValueSet", "id" : "v3-MessageWaitingPriority", "meta" : { "lastUpdated" : "2018-08-12T00:00:00.000+10:00", "profile" : ["http://hl7.org/fhir/StructureDefinition/shareablevalueset"] }, "text" : { "status" : "generated", "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">Release Date: 2018-08-12\r\n<table class=\"grid\">\r\n <tr><td>Level</td><td>Code</td><td>Display</td><td>Definition</td></tr>\r\n <tr><td>1</td><td>H<a name=\"v3-MessageWaitingPriority-H\"> </a></td><td>High</td><td>\n High priority messages are available \r\n\n </td></tr>\r\n <tr><td>1</td><td>L<a name=\"v3-MessageWaitingPriority-L\"> </a></td><td>Low</td><td>\n Low priority messages are available \r\n\n </td></tr>\r\n <tr><td>1</td><td>M<a name=\"v3-MessageWaitingPriority-M\"> </a></td><td>Medium</td><td>\n Medium priority messages are available \r\n\n </td></tr>\r\n</table>\r\n</div>" }, "extension" : [{ "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status", "valueCode" : "external" }, { "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm", "valueInteger" : 0 }, { "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg", "valueCode" : "vocab" }], "url" : "http://terminology.hl7.org/ValueSet/v3-MessageWaitingPriority", "version" : "2018-08-12", "name" : "v3.MessageWaitingPriority", "title" : "v3 Code System MessageWaitingPriority", "status" : "active", "experimental" : false, "date" : "2018-08-12", "publisher" : "HL7, Inc", "contact" : [{ "telecom" : [{ "system" : "url", "value" : "http://hl7.org" }] }], "description" : " Indicates that the receiver has messages for the sender OpenIssue:\r\nDescription does not make sense relative to name of coding system. Must be reviewed and improved.", "immutable" : true, "compose" : { "include" : [{ "system" : "http://terminology.hl7.org/CodeSystem/v3-MessageWaitingPriority" }] } } }, { "fullUrl" : "http://hl7.org/fhir/ValueSet/v3-PaymentTerms", "resource" : { "resourceType" : "ValueSet", "id" : "v3-PaymentTerms", "meta" : { "lastUpdated" : "2018-08-12T00:00:00.000+10:00", "profile" : ["http://hl7.org/fhir/StructureDefinition/shareablevalueset"] }, "text" : { "status" : "generated", "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">Release Date: 2018-08-12\r\n<table class=\"grid\">\r\n <tr><td>Level</td><td>Code</td><td>Display</td><td>Definition</td></tr>\r\n <tr><td>1</td><td>COD<a name=\"v3-PaymentTerms-COD\"> </a></td><td>Cash on Delivery</td><td>\n Payment in full for products and/or services is required as soon as the service is performed or goods delivered. \r\n\n </td></tr>\r\n <tr><td>1</td><td>N30<a name=\"v3-PaymentTerms-N30\"> </a></td><td>Net 30 days</td><td>\n Payment in full for products and/or services is required 30 days from the time the service is performed or goods delivered. \r\n\n </td></tr>\r\n <tr><td>1</td><td>N60<a name=\"v3-PaymentTerms-N60\"> </a></td><td>Net 60 days</td><td>\n Payment in full for products and/or services is required 60 days from the time the service is performed or goods delivered. \r\n\n </td></tr>\r\n <tr><td>1</td><td>N90<a name=\"v3-PaymentTerms-N90\"> </a></td><td>Net 90 days</td><td>\n Payment in full for products and/or services is required 90 days from the time the service is performed or goods delivered. \r\n\n </td></tr>\r\n</table>\r\n</div>" }, "extension" : [{ "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status", "valueCode" : "external" }, { "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm", "valueInteger" : 0 }, { "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg", "valueCode" : "vocab" }], "url" : "http://terminology.hl7.org/ValueSet/v3-PaymentTerms", "identifier" : [{ "system" : "urn:ietf:rfc:3986", "value" : "urn:oid:2.16.840.1.113883.1.11.14908" }], "version" : "2018-08-12", "name" : "v3.PaymentTerms", "title" : "v3 Code System PaymentTerms", "status" : "active", "experimental" : false, "date" : "2018-08-12", "publisher" : "HL7, Inc", "contact" : [{ "telecom" : [{ "system" : "url", "value" : "http://hl7.org" }] }], "description" : " Describes payment terms for a financial transaction, used in an invoice. This is typically expressed as a responsibility of the acceptor or payor of an invoice.", "immutable" : true, "compose" : { "include" : [{ "system" : "http://terminology.hl7.org/CodeSystem/v3-PaymentTerms" }] } } }, { "fullUrl" : "http://hl7.org/fhir/ValueSet/v3-VerificationMethod", "resource" : { "resourceType" : "ValueSet", "id" : "v3-VerificationMethod", "meta" : { "lastUpdated" : "2019-11-01T09:29:23.356+11:00", "profile" : ["http://hl7.org/fhir/StructureDefinition/shareablevalueset"] }, "text" : { "status" : "generated", "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><h2>V3 Value SetVerificationMethod</h2><div>No Description Provided\n</div>This value set includes codes from the following code systems:<ul><li>Include codes from <a href=\"../../v3/ObservationMethod/cs.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ObservationMethod</code></a> where concept is-a <a href=\"../../v3/ObservationMethod/cs.html#v3-ObservationMethod-_VerificationMethod\">_VerificationMethod</a></li></ul></div>" }, "extension" : [{ "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status", "valueCode" : "external" }, { "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm", "valueInteger" : 0 }], "url" : "http://terminology.hl7.org/ValueSet/v3-VerificationMethod", "identifier" : [{ "system" : "urn:ietf:rfc:3986", "value" : "urn:oid:2.16.840.1.113883.1.11.19707" }], "version" : "2014-03-26", "name" : "v3.VerificationMethod", "title" : "V3 Value SetVerificationMethod", "status" : "active", "experimental" : false, "publisher" : "HL7 v3", "contact" : [{ "telecom" : [{ "system" : "url", "value" : "http://www.hl7.org" }] }], "description" : "No Description Provided", "immutable" : false, "compose" : { "include" : [{ "system" : "http://terminology.hl7.org/CodeSystem/v3-ObservationMethod", "filter" : [{ "property" : "concept", "op" : "is-a", "value" : "_VerificationMethod" }] }] } } }, { "fullUrl" : "http://hl7.org/fhir/ValueSet/v3-Ethnicity", "resource" : { "resourceType" : "ValueSet", "id" : "v3-Ethnicity", "meta" : { "lastUpdated" : "2018-08-12T00:00:00.000+10:00", "profile" : ["http://hl7.org/fhir/StructureDefinition/shareablevalueset"] }, "text" : { "status" : "generated", "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">Release Date: 2018-08-12\r\n<table class=\"grid\">\r\n <tr><td>Level</td><td>Code</td><td>Display</td><td>Definition</td></tr>\r\n <tr><td>1</td><td>2135-2<a name=\"v3-Ethnicity-2135-2\"> </a></td><td>Hispanic or Latino</td><td/></tr>\r\n <tr><td>2</td><td> 2137-8<a name=\"v3-Ethnicity-2137-8\"> </a></td><td>Spaniard</td><td/></tr>\r\n <tr><td>3</td><td> 2138-6<a name=\"v3-Ethnicity-2138-6\"> </a></td><td>Andalusian</td><td/></tr>\r\n <tr><td>3</td><td> 2139-4<a name=\"v3-Ethnicity-2139-4\"> </a></td><td>Asturian</td><td/></tr>\r\n <tr><td>3</td><td> 2140-2<a name=\"v3-Ethnicity-2140-2\"> </a></td><td>Castillian</td><td/></tr>\r\n <tr><td>3</td><td> 2141-0<a name=\"v3-Ethnicity-2141-0\"> </a></td><td>Catalonian</td><td/></tr>\r\n <tr><td>3</td><td> 2142-8<a name=\"v3-Ethnicity-2142-8\"> </a></td><td>Belearic Islander</td><td/></tr>\r\n <tr><td>3</td><td> 2143-6<a name=\"v3-Ethnicity-2143-6\"> </a></td><td>Gallego</td><td/></tr>\r\n <tr><td>3</td><td> 2144-4<a name=\"v3-Ethnicity-2144-4\"> </a></td><td>Valencian</td><td/></tr>\r\n <tr><td>3</td><td> 2145-1<a name=\"v3-Ethnicity-2145-1\"> </a></td><td>Canarian</td><td/></tr>\r\n <tr><td>3</td><td> 2146-9<a name=\"v3-Ethnicity-2146-9\"> </a></td><td>Spanish Basque</td><td/></tr>\r\n <tr><td>2</td><td> 2148-5<a name=\"v3-Ethnicity-2148-5\"> </a></td><td>Mexican</td><td/></tr>\r\n <tr><td>3</td><td> 2149-3<a name=\"v3-Ethnicity-2149-3\"> </a></td><td>Mexican American</td><td/></tr>\r\n <tr><td>3</td><td> 2150-1<a name=\"v3-Ethnicity-2150-1\"> </a></td><td>Mexicano</td><td/></tr>\r\n <tr><td>3</td><td> 2151-9<a name=\"v3-Ethnicity-2151-9\"> </a></td><td>Chicano</td><td/></tr>\r\n <tr><td>3</td><td> 2152-7<a name=\"v3-Ethnicity-2152-7\"> </a></td><td>La Raza</td><td/></tr>\r\n <tr><td>3</td><td> 2153-5<a name=\"v3-Ethnicity-2153-5\"> </a></td><td>Mexican American Indian</td><td/></tr>\r\n <tr><td>2</td><td> 2155-0<a name=\"v3-Ethnicity-2155-0\"> </a></td><td>Central American</td><td/></tr>\r\n <tr><td>3</td><td> 2156-8<a name=\"v3-Ethnicity-2156-8\"> </a></td><td>Costa Rican</td><td/></tr>\r\n <tr><td>3</td><td> 2157-6<a name=\"v3-Ethnicity-2157-6\"> </a></td><td>Guatemalan</td><td/></tr>\r\n <tr><td>3</td><td> 2158-4<a name=\"v3-Ethnicity-2158-4\"> </a></td><td>Honduran</td><td/></tr>\r\n <tr><td>3</td><td> 2159-2<a name=\"v3-Ethnicity-2159-2\"> </a></td><td>Nicaraguan</td><td/></tr>\r\n <tr><td>3</td><td> 2160-0<a name=\"v3-Ethnicity-2160-0\"> </a></td><td>Panamanian</td><td/></tr>\r\n <tr><td>3</td><td> 2161-8<a name=\"v3-Ethnicity-2161-8\"> </a></td><td>Salvadoran</td><td/></tr>\r\n <tr><td>3</td><td> 2162-6<a name=\"v3-Ethnicity-2162-6\"> </a></td><td>Central American Indian</td><td/></tr>\r\n <tr><td>3</td><td> 2163-4<a name=\"v3-Ethnicity-2163-4\"> </a></td><td>Canal Zone</td><td/></tr>\r\n <tr><td>2</td><td> 2165-9<a name=\"v3-Ethnicity-2165-9\"> </a></td><td>South American</td><td/></tr>\r\n <tr><td>3</td><td> 2166-7<a name=\"v3-Ethnicity-2166-7\"> </a></td><td>Argentinean</td><td/></tr>\r\n <tr><td>3</td><td> 2167-5<a name=\"v3-Ethnicity-2167-5\"> </a></td><td>Bolivian</td><td/></tr>\r\n <tr><td>3</td><td> 2168-3<a name=\"v3-Ethnicity-2168-3\"> </a></td><td>Chilean</td><td/></tr>\r\n <tr><td>3</td><td> 2169-1<a name=\"v3-Ethnicity-2169-1\"> </a></td><td>Colombian</td><td/></tr>\r\n <tr><td>3</td><td> 2170-9<a name=\"v3-Ethnicity-2170-9\"> </a></td><td>Ecuadorian</td><td/></tr>\r\n <tr><td>3</td><td> 2171-7<a name=\"v3-Ethnicity-2171-7\"> </a></td><td>Paraguayan</td><td/></tr>\r\n <tr><td>3</td><td> 2172-5<a name=\"v3-Ethnicity-2172-5\"> </a></td><td>Peruvian</td><td/></tr>\r\n <tr><td>3</td><td> 2173-3<a name=\"v3-Ethnicity-2173-3\"> </a></td><td>Uruguayan</td><td/></tr>\r\n <tr><td>3</td><td> 2174-1<a name=\"v3-Ethnicity-2174-1\"> </a></td><td>Venezuelan</td><td/></tr>\r\n <tr><td>3</td><td> 2175-8<a name=\"v3-Ethnicity-2175-8\"> </a></td><td>South American Indian</td><td/></tr>\r\n <tr><td>3</td><td> 2176-6<a name=\"v3-Ethnicity-2176-6\"> </a></td><td>Criollo</td><td/></tr>\r\n <tr><td>2</td><td> 2178-2<a name=\"v3-Ethnicity-2178-2\"> </a></td><td>Latin American</td><td/></tr>\r\n <tr><td>2</td><td> 2180-8<a name=\"v3-Ethnicity-2180-8\"> </a></td><td>Puerto Rican</td><td/></tr>\r\n <tr><td>2</td><td> 2182-4<a name=\"v3-Ethnicity-2182-4\"> </a></td><td>Cuban</td><td/></tr>\r\n <tr><td>2</td><td> 2184-0<a name=\"v3-Ethnicity-2184-0\"> </a></td><td>Dominican</td><td/></tr>\r\n <tr><td>1</td><td>2186-5<a name=\"v3-Ethnicity-2186-5\"> </a></td><td>Not Hispanic or Latino</td><td>\n Note that this term remains in the table for completeness, even though within HL7, the notion of "not otherwise coded" term is deprecated. \r\n\n </td></tr>\r\n</table>\r\n</div>" }, "extension" : [{ "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status", "valueCode" : "external" }, { "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm", "valueInteger" : 0 }, { "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg", "valueCode" : "vocab" }], "url" : "http://terminology.hl7.org/ValueSet/v3-Ethnicity", "version" : "2018-08-12", "name" : "v3.Ethnicity", "title" : "v3 Code System Ethnicity", "status" : "active", "experimental" : false, "date" : "2018-08-12", "publisher" : "HL7, Inc", "contact" : [{ "telecom" : [{ "system" : "url", "value" : "http://hl7.org" }] }], "description" : " In the United States, federal standards for classifying data on ethnicity determine the categories used by federal agencies and exert a strong influence on categorization by state and local agencies and private sector organizations. The federal standards do not conceptually define ethnicity, and they recognize the absence of an anthropological or scientific basis for ethnicity classification. Instead, the federal standards acknowledge that ethnicity is a social-political construct in which an individual's own identification with a particular ethnicity is preferred to observer identification. The standards specify two minimum ethnicity categories: Hispanic or Latino, and Not Hispanic or Latino. The standards define a Hispanic or Latino as a person of \"Mexican, Puerto Rican, Cuban, South or Central America, or other Spanish culture or origin, regardless of race.\" The standards stipulate that ethnicity data need not be limited to the two minimum categories, but any expansion must be collapsible to those categories. In addition, the standards stipulate that an individual can be Hispanic or Latino or can be Not Hispanic or Latino, but cannot be both.", "immutable" : true, "compose" : { "include" : [{ "system" : "http://terminology.hl7.org/CodeSystem/v3-Ethnicity" }] } } }, { "fullUrl" : "http://hl7.org/fhir/ValueSet/v3-NullFlavor", "resource" : { "resourceType" : "ValueSet", "id" : "v3-NullFlavor", "meta" : { "lastUpdated" : "2018-08-12T00:00:00.000+10:00", "profile" : ["http://hl7.org/fhir/StructureDefinition/shareablevalueset"] }, "text" : { "status" : "generated", "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">Release Date: 2018-08-12\r\n<table class=\"grid\">\r\n <tr><td>Level</td><td>Code</td><td>Display</td><td>Definition</td></tr>\r\n <tr><td>1</td><td>NI<a name=\"v3-NullFlavor-NI\"> </a></td><td>NoInformation</td><td>\n \n Description:The value is exceptional (missing, omitted, incomplete, improper). No information as to the reason for being an exceptional value is provided. This is the most general exceptional value. It is also the default exceptional value. \r\n\n </td></tr>\r\n <tr><td>2</td><td> INV<a name=\"v3-NullFlavor-INV\"> </a></td><td>invalid</td><td>\n \n Description:The value as represented in the instance is not a member of the set of permitted data values in the constrained value domain of a variable. \r\n\n </td></tr>\r\n <tr><td>3</td><td> DER<a name=\"v3-NullFlavor-DER\"> </a></td><td>derived</td><td>\n \n Description:An actual value may exist, but it must be derived from the provided information (usually an EXPR generic data type extension will be used to convey the derivation expressionexpression . \r\n\n </td></tr>\r\n <tr><td>3</td><td> OTH<a name=\"v3-NullFlavor-OTH\"> </a></td><td>other</td><td>\n \n Description:The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system). \r\n\n \n Usage Notes: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. \r\n\n With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE. \r\n\n </td></tr>\r\n <tr><td>4</td><td> NINF<a name=\"v3-NullFlavor-NINF\"> </a></td><td>negative infinity</td><td>\n Negative infinity of numbers. \r\n\n </td></tr>\r\n <tr><td>4</td><td> PINF<a name=\"v3-NullFlavor-PINF\"> </a></td><td>positive infinity</td><td>\n Positive infinity of numbers. \r\n\n </td></tr>\r\n <tr><td>3</td><td> UNC<a name=\"v3-NullFlavor-UNC\"> </a></td><td>un-encoded</td><td>\n \n Description: The actual value has not yet been encoded within the approved value domain. \r\n\n \n Example: Original text or a local code has been specified but translation or encoding to the approved value set has not yet occurred due to limitations of the sending system. Original text has been captured for a PQ, but not attempt has been made to split the value and unit or to encode the unit in UCUM. \r\n\n \n Usage Notes: If it is known that it is not possible to encode the concept, OTH should be used instead. However, use of UNC does not necessarily guarantee the concept will be encodable, only that encoding has not been attempted. \r\n\n Data type properties such as original text and translations may be present when this null flavor is included. \r\n\n </td></tr>\r\n <tr><td>2</td><td> MSK<a name=\"v3-NullFlavor-MSK\"> </a></td><td>masked</td><td>\n There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons. There may be an alternate mechanism for gaining access to this information. \r\n\n Note: using this null flavor does provide information that may be a breach of confidentiality, even though no detail data is provided. Its primary purpose is for those circumstances where it is necessary to inform the receiver that the information does exist without providing any detail. \r\n\n </td></tr>\r\n <tr><td>2</td><td> NA<a name=\"v3-NullFlavor-NA\"> </a></td><td>not applicable</td><td>\n Known to have no proper value (e.g., last menstrual period for a male). \r\n\n </td></tr>\r\n <tr><td>2</td><td> UNK<a name=\"v3-NullFlavor-UNK\"> </a></td><td>unknown</td><td>\n \n Description:A proper value is applicable, but not known. \r\n\n \n Usage Notes: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless: \r\n\n \n Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown')\n Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.)\n \n </td></tr>\r\n <tr><td>3</td><td> ASKU<a name=\"v3-NullFlavor-ASKU\"> </a></td><td>asked but unknown</td><td>\n Information was sought but not found (e.g., patient was asked but didn't know) \r\n\n </td></tr>\r\n <tr><td>4</td><td> NAV<a name=\"v3-NullFlavor-NAV\"> </a></td><td>temporarily unavailable</td><td>\n Information is not available at this time but it is expected that it will be available later. \r\n\n </td></tr>\r\n <tr><td>3</td><td> NASK<a name=\"v3-NullFlavor-NASK\"> </a></td><td>not asked</td><td>\n This information has not been sought (e.g., patient was not asked) \r\n\n </td></tr>\r\n <tr><td>3</td><td> NAVU<a name=\"v3-NullFlavor-NAVU\"> </a></td><td>Not available</td><td>\n Information is not available at this time (with no expectation regarding whether it will or will not be available in the future). \r\n\n </td></tr>\r\n <tr><td>4</td><td> <a href=\"#NAV\">NAV</a></td><td/><td/></tr>\r\n <tr><td>3</td><td> QS<a name=\"v3-NullFlavor-QS\"> </a></td><td>Sufficient Quantity</td><td>\n \n Description:The specific quantity is not known, but is known to be non-zero and is not specified because it makes up the bulk of the material. e.g. 'Add 10mg of ingredient X, 50mg of ingredient Y, and sufficient quantity of water to 100mL.' The null flavor would be used to express the quantity of water. \r\n\n </td></tr>\r\n <tr><td>3</td><td> TRC<a name=\"v3-NullFlavor-TRC\"> </a></td><td>trace</td><td>\n The content is greater than zero, but too small to be quantified. \r\n\n </td></tr>\r\n <tr><td>1</td><td>NP<a name=\"v3-NullFlavor-NP\"> </a></td><td>not present</td><td>\n Value is not present in a message. This is only defined in messages, never in application data! All values not present in the message must be replaced by the applicable default, or no-information (NI) as the default of all defaults. \r\n\n </td></tr>\r\n</table>\r\n</div>" }, "extension" : [{ "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status", "valueCode" : "external" }, { "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm", "valueInteger" : 0 }, { "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg", "valueCode" : "vocab" }], "url" : "http://terminology.hl7.org/ValueSet/v3-NullFlavor", "identifier" : [{ "system" : "urn:ietf:rfc:3986", "value" : "urn:oid:2.16.840.1.113883.1.11.10609" }], "version" : "2018-08-12", "name" : "v3.NullFlavor", "title" : "v3 Code System NullFlavor", "status" : "active", "experimental" : false, "date" : "2018-08-12", "publisher" : "HL7, Inc", "contact" : [{ "telecom" : [{ "system" : "url", "value" : "http://hl7.org" }] }], "description" : " A collection of codes specifying why a valid value is not present.", "immutable" : true, "compose" : { "include" : [{ "system" : "http://terminology.hl7.org/CodeSystem/v3-NullFlavor" }] } } }, { "fullUrl" : "http://hl7.org/fhir/ValueSet/v3-ActRelationshipType", "resource" : { "resourceType" : "ValueSet", "id" : "v3-ActRelationshipType", "meta" : { "lastUpdated" : "2018-08-12T00:00:00.000+10:00", "profile" : ["http://hl7.org/fhir/StructureDefinition/shareablevalueset"] }, "text" : { "status" : "generated", "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">Release Date: 2018-08-12\r\n<table class=\"grid\">\r\n <tr><td>Level</td><td>Code</td><td>Display</td><td>Definition</td></tr>\r\n <tr><td>1</td><td>ART<a name=\"v3-ActRelationshipType-ART\"> </a></td><td>act relationship type</td><td>\n \n Description: A directed association between a source Act and a target Act. \r\n\n \n Usage Note: This code should never be transmitted in an instance as the value of ActRelationship.typeCode (attribute) \r\n\n </td></tr>\r\n <tr><td>2</td><td> (_ActClassTemporallyPertains) Abstract</td><td><a name=\"v3-ActRelationshipType-_ActClassTemporallyPertains\"> </a></td><td/></tr>\r\n <tr><td>2</td><td> (_ActRelationshipAccounting) Abstract</td><td><a name=\"v3-ActRelationshipType-_ActRelationshipAccounting\"> </a></td><td>\n Codes that describe the relationship between an Act and a financial instrument such as a financial transaction, account or invoice element. \r\n\n </td></tr>\r\n <tr><td>3</td><td> (_ActRelationshipCostTracking) Abstract</td><td><a name=\"v3-ActRelationshipType-_ActRelationshipCostTracking\"> </a></td><td>\n Expresses values for describing the relationship relationship between an InvoiceElement or InvoiceElementGroup and a billable act. \r\n\n </td></tr>\r\n <tr><td>4</td><td> CHRG<a name=\"v3-ActRelationshipType-CHRG\"> </a></td><td>has charge</td><td>\n A relationship that provides an ability to associate a financial transaction (target) as a charge to a clinical act (source). A clinical act may have a charge associated with the execution or delivery of the service. \r\n\n The financial transaction will define the charge (bill) for delivery or performance of the service. \r\n\n Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product. \r\n\n </td></tr>\r\n <tr><td>4</td><td> COST<a name=\"v3-ActRelationshipType-COST\"> </a></td><td>has cost</td><td>\n A relationship that provides an ability to associate a financial transaction (target) as a cost to a clinical act (source). A clinical act may have an inherit cost associated with the execution or delivery of the service. \r\n\n The financial transaction will define the cost of delivery or performance of the service. \r\n\n Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product. \r\n\n </td></tr>\r\n <tr><td>3</td><td> (_ActRelationshipPosting) Abstract</td><td><a name=\"v3-ActRelationshipType-_ActRelationshipPosting\"> </a></td><td>\n Expresses values for describing the relationship between a FinancialTransaction and an Account. \r\n\n </td></tr>\r\n <tr><td>4</td><td> CREDIT<a name=\"v3-ActRelationshipType-CREDIT\"> </a></td><td>has credit</td><td>\n A credit relationship ties a financial transaction (target) to an account (source). A credit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account credit will decrease the account balance. A non-asset account credit will decrease the account balance. \r\n\n </td></tr>\r\n <tr><td>4</td><td> DEBIT<a name=\"v3-ActRelationshipType-DEBIT\"> </a></td><td>has debit</td><td>\n A debit relationship ties a financial transaction (target) to an account (source). A debit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account debit will increase the account balance. A non-asset account debit will decrease the account balance. \r\n\n </td></tr>\r\n <tr><td>2</td><td> (_ActRelationshipConditional) Abstract</td><td><a name=\"v3-ActRelationshipType-_ActRelationshipConditional\"> </a></td><td>\n Specifies under what circumstances (target Act) the source-Act may, must, must not or has occurred \r\n\n </td></tr>\r\n <tr><td>3</td><td> CIND<a name=\"v3-ActRelationshipType-CIND\"> </a></td><td>has contra-indication</td><td>\n A contraindication is just a negation of a reason, i.e. it gives a condition under which the action is not to be done. Both, source and target can be any kind of service; target service is in criterion mood. How the strength of a contraindication is expressed (e.g., relative, absolute) is left as an open issue. The priorityNumber attribute could be used. \r\n\n </td></tr>\r\n <tr><td>3</td><td> PRCN<a name=\"v3-ActRelationshipType-PRCN\"> </a></td><td>has pre-condition</td><td>\n A requirement to be true before a service is performed. The target can be any service in criterion mood. For multiple pre-conditions a conjunction attribute (AND, OR, XOR) is applicable. \r\n\n </td></tr>\r\n <tr><td>3</td><td> RSON<a name=\"v3-ActRelationshipType-RSON\"> </a></td><td>has reason</td><td>\n \n Description: The reason or rationale for a service. A reason link is weaker than a trigger, it only suggests that some service may be or might have been a reason for some action, but not that this reason requires/required the action to be taken. Also, as opposed to the trigger, there is no strong timely relation between the reason and the action. As well as providing various types of information about the rationale for a service, the RSON act relationship is routinely used between a SBADM act and an OBS act to describe the indication for use of a medication. Child concepts may be used to describe types of indication. \r\n\n \n Discussion: In prior releases, the code "SUGG" (suggests) was expressed as "an inversion of the reason link." That code has been retired in favor of the inversion indicator that is an attribute of ActRelationship. \r\n\n </td></tr>\r\n <tr><td>4</td><td> BLOCK<a name=\"v3-ActRelationshipType-BLOCK\"> </a></td><td>blocks</td><td>\n \n Definition: The source act is performed to block the effects of the target act. This act relationship should be used when describing near miss type incidents where potential harm could have occurred, but the action described in the source act blocked the potential harmful effects of the incident actually occurring. \r\n\n </td></tr>\r\n <tr><td>4</td><td> DIAG<a name=\"v3-ActRelationshipType-DIAG\"> </a></td><td>diagnoses</td><td>\n \n Description: The source act is intended to help establish the presence of a (an adverse) situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. \r\n\n </td></tr>\r\n <tr><td>4</td><td> IMM<a name=\"v3-ActRelationshipType-IMM\"> </a></td><td>immunization against</td><td>\n \n Description: The source act is intented to provide immunity against the effects of the target act (the target act describes an infectious disease) \r\n\n </td></tr>\r\n <tr><td>5</td><td> ACTIMM<a name=\"v3-ActRelationshipType-ACTIMM\"> </a></td><td>active immunization against</td><td>\n \n Description: The source act is intended to provide active immunity against the effects of the target act (the target act describes an infectious disease) \r\n\n </td></tr>\r\n <tr><td>5</td><td> PASSIMM<a name=\"v3-ActRelationshipType-PASSIMM\"> </a></td><td>passive immunization against</td><td>\n \n Description: The source act is intended to provide passive immunity against the effects of the target act (the target act describes an infectious disease). \r\n\n </td></tr>\r\n <tr><td>4</td><td> MITGT<a name=\"v3-ActRelationshipType-MITGT\"> </a></td><td>mitigates</td><td>\n The source act removes or lessens the occurrence or effect of the target act. \r\n\n </td></tr>\r\n <tr><td>5</td><td> RCVY<a name=\"v3-ActRelationshipType-RCVY\"> </a></td><td>recovers</td><td>\n \n Definition: The source act is performed to recover from the effects of the target act. \r\n\n </td></tr>\r\n <tr><td>4</td><td> PRYLX<a name=\"v3-ActRelationshipType-PRYLX\"> </a></td><td>prophylaxis of</td><td>\n \n Description: The source act is intended to reduce the risk of of an adverse situation to emerge as described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. \r\n\n </td></tr>\r\n <tr><td>4</td><td> TREAT<a name=\"v3-ActRelationshipType-TREAT\"> </a></td><td>treats</td><td>\n \n Description: The source act is intended to improve a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. \r\n\n </td></tr>\r\n <tr><td>5</td><td> ADJUNCT<a name=\"v3-ActRelationshipType-ADJUNCT\"> </a></td><td>adjunctive treatment</td><td>\n \n Description: The source act is intended to offer an additional treatment for the management or cure of a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. It is not a requirement that the non-adjunctive treatment is explicitly specified. \r\n\n </td></tr>\r\n <tr><td>5</td><td> MTREAT<a name=\"v3-ActRelationshipType-MTREAT\"> </a></td><td>maintenance treatment</td><td>\n \n Description: The source act is intended to provide long term maintenance improvement or management of a pre-existing adverse situation described by the target act. This is not limited to diseases but can apply to any adverse situation or condition of medical or technical nature. \r\n\n </td></tr>\r\n <tr><td>5</td><td> PALLTREAT<a name=\"v3-ActRelationshipType-PALLTREAT\"> </a></td><td>palliates</td><td>\n \n Description: The source act is intended to provide palliation for the effects of the target act. \r\n\n </td></tr>\r\n <tr><td>5</td><td> SYMP<a name=\"v3-ActRelationshipType-SYMP\"> </a></td><td>symptomatic relief</td><td>\n \n Description: The source act is intented to provide symptomatic relief for the effects of the target act. \r\n\n </td></tr>\r\n <tr><td>3</td><td> TRIG<a name=\"v3-ActRelationshipType-TRIG\"> </a></td><td>has trigger</td><td>\n A pre-condition that if true should result in the source Act being executed. The target is in typically in criterion mood. When reported after the fact (i.e. the criterion has been met) it may be in Event mood. A delay between the trigger and the triggered action can be specified. \r\n\n \n Discussion: This includes the concept of a required act for a service or financial instrument such as an insurance plan or policy. In such cases, the trigger is the occurrence of a specific condition such as coverage limits being exceeded. \r\n\n </td></tr>\r\n <tr><td>2</td><td> (_ActRelationshipTemporallyPertains) Abstract</td><td><a name=\"v3-ActRelationshipType-_ActRelationshipTemporallyPertains\"> </a></td><td>\n Abstract collector for ActRelationhsip types that relate two acts by their timing. \r\n\n </td></tr>\r\n <tr><td>3</td><td> (_ActRelationshipTemporallyPertainsApproximates) Abstract</td><td><a name=\"v3-ActRelationshipType-_ActRelationshipTemporallyPertainsApproximates\"> </a></td><td>\n Abstract collector for ActRelationship types that relate two acts by their approximate timing. \r\n\n </td></tr>\r\n <tr><td>4</td><td> ENE<a name=\"v3-ActRelationshipType-ENE\"> </a></td><td>ends near end</td><td>\n A relationship in which the source act's effective time ends near the end of the target act's effective time. Near is defined separately as a time interval. \r\n\n \n Usage Note: Inverse code is ENS \r\n\n </td></tr>\r\n <tr><td>5</td><td> ECW<a name=\"v3-ActRelationshipType-ECW\"> </a></td><td>ends concurrent with</td><td>\n A relationship in which the source act's effective time ends with the end of the target act's effective time. \r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself. \r\n\n </td></tr>\r\n <tr><td>6</td><td> CONCURRENT<a name=\"v3-ActRelationshipType-CONCURRENT\"> </a></td><td>concurrent with</td><td>\n A relationship in which the source act's effective time is the same as the target act's effective time. \r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself. \r\n\n </td></tr>\r\n <tr><td>6</td><td> SBSECWE<a name=\"v3-ActRelationshipType-SBSECWE\"> </a></td><td>starts before start of, ends with</td><td>\n The source Act starts before the start of the target Act, and ends with the target Act. \r\n\n \n UsageNote: Inverse code is SASECWE\n \r\n\n </td></tr>\r\n <tr><td>4</td><td> ENS<a name=\"v3-ActRelationshipType-ENS\"> </a></td><td>ends near start</td><td>\n A relationship in which the source act's effective time ends near the start of the target act's effective time. Near is defined separately as a time interval. \r\n\n \n Usage Note: Inverse code is ENE \r\n\n </td></tr>\r\n <tr><td>5</td><td> ECWS<a name=\"v3-ActRelationshipType-ECWS\"> </a></td><td>ends concurrent with start of</td><td>\n The source Act ends when the target act starts (i.e. if we say "ActOne ECWS ActTwo", it means that ActOne ends when ActTwo starts, therefore ActOne is the source and ActTwo is the target). \r\n\n \n UsageNote: Inverse code is SCWE\n \r\n\n </td></tr>\r\n <tr><td>4</td><td> SNE<a name=\"v3-ActRelationshipType-SNE\"> </a></td><td>starts near end</td><td>\n A relationship in which the source act's effective time starts near the end of the target act's effective time. Near is defined separately as a time interval. \r\n\n \n Usage Note: Inverse code is SNS \r\n\n </td></tr>\r\n <tr><td>5</td><td> SCWE<a name=\"v3-ActRelationshipType-SCWE\"> </a></td><td>starts concurrent with end of</td><td>\n The source Act starts when the target act ends (i.e. if we say "ActOne SCWE ActTwo", it means that ActOne starts when ActTwo ends, therefore ActOne is the source and ActTwo is the target). \r\n\n \n UsageNote: Inverse code is SBSECWS\n \r\n\n </td></tr>\r\n <tr><td>4</td><td> SNS<a name=\"v3-ActRelationshipType-SNS\"> </a></td><td>starts near start</td><td>\n A relationship in which the source act's effective time starts near the start of the target act's effective time. Near is defined separately as a time interval. \r\n\n \n Usage Note: Inverse code is SNE \r\n\n </td></tr>\r\n <tr><td>5</td><td> SCW<a name=\"v3-ActRelationshipType-SCW\"> </a></td><td>starts concurrent with</td><td>\n A relationship in which the source act's effective time starts with the start of the target act's effective time. \r\n\n \n UsageNote: This code is reflexive. Therefore its inverse code is itself. \r\n\n </td></tr>\r\n <tr><td>6</td><td> <a href=\"#CONCURRENT\">CONCURRENT</a></td><td/><td/></tr>\r\n <tr><td>6</td><td> SCWSEBE<a name=\"v3-ActRelationshipType-SCWSEBE\"> </a></td><td>starts with. ends before end of</td><td>\n The source Act starts with.the target Act and ends before the end of the target Act. \r\n\n \n UsageNote: Inverse code is SCWSEAE\n \r\n\n </td></tr>\r\n <tr><td>6</td><td> SCWSEAE<a name=\"v3-ActRelationshipType-SCWSEAE\"> </a></td><td>starts with, ends after end of</td><td>The source Act starts with the target Act, and ends after the end of the target Act.</td></tr>\r\n <tr><td>3</td><td> EAS<a name=\"v3-ActRelationshipType-EAS\"> </a></td><td>ends after start of</td><td>\n A relationship in which the source act ends after the target act starts. \r\n\n \n UsageNote: Inverse code is SBE\n \r\n\n </td></tr>\r\n <tr><td>4</td><td> EAE<a name=\"v3-ActRelationshipType-EAE\"> </a></td><td>ends after end of</td><td>\n A relationship in which the source act ends after the target act ends. \r\n\n \n UsageNote: Inverse code is EBE\n \r\n\n </td></tr>\r\n <tr><td>5</td><td> SASEAE<a name=\"v3-ActRelationshipType-SASEAE\"> </a></td><td>starts after start of, ends after end of</td><td>\n The source Act starts after start of the target Act and ends after end of the target Act. \r\n\n \n UsageNote: Inverse code is SBSEBE\n \r\n\n </td></tr>\r\n <tr><td>6</td><td> SBEEAE<a name=\"v3-ActRelationshipType-SBEEAE\"> </a></td><td>contains end of</td><td>\n The source Act contains the end of the target Act. \r\n\n \n UsageNote: Inverse code is EDU\n \r\n\n </td></tr>\r\n <tr><td>7</td><td> SASSBEEAS<a name=\"v3-ActRelationshipType-SASSBEEAS\"> </a></td><td>start after start of, contains end of</td><td>\n The source Act start after the start of the target Act, and contains the end of the target Act. \r\n\n \n UsageNote: Inverse code is SBSEASEBE\n \r\n\n </td></tr>\r\n <tr><td>7</td><td> SBSEAE<a name=\"v3-ActRelationshipType-SBSEAE\"> </a></td><td>contains time of</td><td>\n The source Act contains the time of the target Act. \r\n\n \n UsageNote: Inverse code is DURING\n \r\n\n </td></tr>\r\n <tr><td>7</td><td> <a href=\"#SCWSEAE\">SCWSEAE</a></td><td/><td/></tr>\r\n <tr><td>6</td><td> <a href=\"#SASSBEEAS\">SASSBEEAS</a></td><td/><td/></tr>\r\n <tr><td>4</td><td> SAS<a name=\"v3-ActRelationshipType-SAS\"> </a></td><td>starts after start of</td><td>\n The source Act starts after the start of the target Act (i.e. if we say "ActOne SAS ActTwo", it means that ActOne starts after the start of ActTwo, therefore ActOne is the source and ActTwo is the target). \r\n\n \n UsageNote: Inverse code is SBS\n \r\n\n </td></tr>\r\n <tr><td>5</td><td> <a href=\"#SASEAE\">SASEAE</a></td><td/><td/></tr>\r\n <tr><td>5</td><td> SAE<a name=\"v3-ActRelationshipType-SAE\"> </a></td><td>starts after end of</td><td>\n A relationship in which the source act starts after the target act ends. \r\n\n \n UsageNote: Inverse code is EBS\n \r\n\n </td></tr>\r\n <tr><td>5</td><td> DURING<a name=\"v3-ActRelationshipType-DURING\"> </a></td><td>occurs during</td><td>\n A relationship in which the source act's effective time is wholly within the target act's effective time (including end points, as defined in the act's effective times) \r\n\n \n UsageNote: Inverse code is SBSEAE\n \r\n\n </td></tr>\r\n <tr><td>5</td><td> SASECWE<a name=\"v3-ActRelationshipType-SASECWE\"> </a></td><td>starts after start of, ends with</td><td>\n The source Act starts after start of the target Act, and ends with the target Act. \r\n\n \n UsageNote: Inverse code is SBSECWE\n \r\n\n </td></tr>\r\n <tr><td>3</td><td> EASORECWS<a name=\"v3-ActRelationshipType-EASORECWS\"> </a></td><td>ends after or concurrent with start of</td><td>\n A relationship in which the source act's effective time ends after or concurrent with the start of the target act's effective time. \r\n\n \n Usage Note: Inverse code is EBSORECWS \r\n\n </td></tr>\r\n <tr><td>4</td><td> <a href=\"#EAS\">EAS</a></td><td/><td/></tr>\r\n <tr><td>4</td><td> EAEORECW<a name=\"v3-ActRelationshipType-EAEORECW\"> </a></td><td>ends after or concurrent with end of</td><td>\n A relationship in which the source act's effective time ends after or concurrent with the end of the target act's effective time. \r\n\n \n Usage Note: Inverse code is EBEORECW \r\n\n </td></tr>\r\n <tr><td>5</td><td> <a href=\"#EAE\">EAE</a></td><td/><td/></tr>\r\n <tr><td>5</td><td>