6.1.5. Slucaj
Podatci o zdravstvenom slučaju.
Koncept Slučaja predstavlja određeni zdravstveni problem ili stanje pacijenta u određenom trenutku u vremenu. Slučaj je definiran sa tri osnovna atributa: dijagnoza, vrijeme početka i završetka problema odnosno stanja te status slučaja.
Domenski model podataka o Slučaju prikazan je na slijedećoj slici.
Kako je prikazano na slici 1 podatci o slučaju se sastoje od
- jedinstvenog identifikatora slučaja kojeg dodjeljuje ova usluga prilikom kreiranja slučaja (identifier)
- datum završetka slučaja (abatement date)
- datum početka slučaja (onset date)
- datum kada je slučaj zabilježen (recorded date)
- status slučaja (clinical status)
- status verifikacije slučaja (verification status)
- dijagnoza (identification of HI)
- vezani slučaj (related)
- posjeta u kojoj je identificiran slučaj (encounter)
- pacijent (subject)
- liječnik koji je identificirao slučaj (asserter)
- liječnik koji je zabilježio slučaj (recorder)
Na slijedećoj slici su prikazana stanja slučaja (clinical status).
| Slika 2 - Model stanja |
The resource cannot be rendered.
The resource cannot be rendered.
</meta>
--- We have skipped the narrative for better readability of the resource ---
</text>
</telecom>
</contact>
<description value="Podatci o zdravstvenom slučaju.\n\nKoncept Slučaja predstavlja određeni zdravstveni problem ili stanje pacijenta u određenom trenutku u vremenu. Slučaj je definiran sa tri osnovna atributa: dijagnoza, vrijeme početka i završetka problema odnosno stanja te status slučaja. \n\nDomenski model podataka o Slučaju prikazan je na slijedećoj slici.\n\n<table>\n<tr><td><img style="max-width:100%" src="HI Domain Model.jpg" /></td></tr>\n<tr><td>Slika 1 - Domenski model podataka o slučaju</td></tr>\n</table>\nKako je prikazano na slici 1 podatci o slučaju se sastoje od \n* jedinstvenog identifikatora slučaja kojeg dodjeljuje ova usluga prilikom kreiranja slučaja (identifier)\n* datum završetka slučaja (abatement date)\n* datum početka slučaja (onset date)\n* datum kada je slučaj zabilježen (recorded date)\n* status slučaja (clinical status)\n* status verifikacije slučaja (verification status)\n* dijagnoza (identification of HI)\n* vezani slučaj (related)\n* posjeta u kojoj je identificiran slučaj (encounter)\n* pacijent (subject)\n* liječnik koji je identificirao slučaj (asserter)\n* liječnik koji je zabilježio slučaj (recorder)\n\nNa slijedećoj slici su prikazana stanja slučaja (clinical status).\n\n<table>\n<tr><td><img style="max-width:100%" src="HI State Model.jpg" /></td></tr>\n<tr><td>Slika 2 - Model stanja</td></tr>\n</table>" />
</coding>
</jurisdiction>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
<definition value="A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern." />
</base>
</extension>
<extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-bestpractice-explanation">
<valueMarkdown value="Most systems will expect a clinicalStatus to be valued for problem-list-items that are managed over time, but might not need a clinicalStatus for point in time encounter-diagnosis." />
</extension>
<human value="Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item" />
<expression value="clinicalStatus.exists() or verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code = 'entered-in-error').exists() or category.select($this='problem-list-item').empty()" />
<xpath value="exists(f:clinicalStatus) or exists(f:verificationStatus/f:coding/f:code/@value='entered-in-error') or not(exists(category[@value='problem-list-item']))" />
</constraint>
<human value="If condition is abated, then clinicalStatus must be either inactive, resolved, or remission" />
<expression value="abatement.empty() or clinicalStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-clinical' and (code='resolved' or code='remission' or code='inactive')).exists()" />
<xpath value="not(exists(*[starts-with(local-name(.), 'abatement')])) or exists(f:clinicalStatus/f:coding[f:system/@value='http://terminology.hl7.org/CodeSystem/condition-clinical' and f:code/@value=('resolved', 'remission', 'inactive')])" />
</constraint>
<human value="Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error" />
<expression value="verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code='entered-in-error').empty() or clinicalStatus.empty()" />
<xpath value="not(exists(f:verificationStatus/f:coding[f:system/@value='http://terminology.hl7.org/CodeSystem/condition-ver-status' and f:code/@value='entered-in-error'])) or not(exists(f:clinicalStatus))" />
</constraint>
<human value="If the resource is contained in another resource, it SHALL NOT contain nested Resources" />
</constraint>
<human value="If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource" />
<expression value="contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()" />
<xpath value="not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))" />
</constraint>
<human value="If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated" />
<xpath value="not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))" />
</constraint>
<human value="If a resource is contained in another resource, it SHALL NOT have a security label" />
</constraint>
</extension>
<extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-bestpractice-explanation">
<valueMarkdown value="When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time." />
</extension>
</constraint>
</mapping>
</mapping>
<map value="< 243796009 |Situation with explicit context| : 246090004 |Associated finding| = ( ( < 404684003 |Clinical finding| MINUS ( << 420134006 |Propensity to adverse reactions| OR << 473010000 |Hypersensitivity condition| OR << 79899007 |Drug interaction| OR << 69449002 |Drug action| OR << 441742003 |Evaluation finding| OR << 307824009 |Administrative status| OR << 385356007 |Tumor stage finding|)) OR < 272379006 |Event|)" />
</mapping>
</mapping>
</mapping>
</element>
<definition value="The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes." />
<comment value="The only time that a resource does not have an id is when it is being submitted to the server using a create operation." />
</base>
</extension>
</type>
</element>
<definition value="The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource." />
</base>
</type>
</constraint>
</element>
<definition value="A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc." />
<comment value="Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc." />
</base>
</type>
</constraint>
</element>
<comment value="Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)." />
</base>
</type>
</constraint>
</extension>
</extension>
</binding>
</element>
<definition value="A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety." />
<comment value="Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later." />
</base>
</type>
</constraint>
</mapping>
</element>
<definition value="These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope." />
<comment value="This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels." />
</base>
</type>
</mapping>
</element>
</slicing>
</base>
</type>
</constraint>
</constraint>
</element>
<definition value="Ekstenzija definira vezu i tip veze prema drugom slučaju zdravlja (Health Issue). Predmetni slučaj može biti komplikacija, komorbiditet, zamjena itd. slučaja prema kojem ima vezu (referencu)." />
</base>
</type>
</constraint>
</constraint>
</element>
<definition value="May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself)." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
<requirements value="Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension)." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="Business identifiers assigned to this condition by the performer or other systems which remain constant as the resource is updated and propagates from server to server." />
<comment value="This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R4/resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number." />
<requirements value="Allows identification of the condition as it is known by various participating systems and in a way that remains consistent across servers." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Ovaj identifikator dodjeljuje usluga "Upravljanje slučajevima" prilikom kreiranja novog slučaja ili kreiranja ponovljenog slučaja. Ovaj identifikator se smatra globalno jedinstven i nemogu postojati dva slučaja sa istim identifikatorom ovog tipa." />
<comment value="This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R4/resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number." />
<requirements value="Allows identification of the condition as it is known by various participating systems and in a way that remains consistent across servers." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
<comment value="Applications can assume that an identifier is permanent unless it explicitly says that it is temporary." />
<requirements value="Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers." />
</base>
</type>
</constraint>
</extension>
</binding>
</mapping>
</mapping>
</element>
<definition value="A coded type for the identifier that can be used to determine which identifier to use for a specific purpose." />
<comment value="This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type." />
<requirements value="Allows users to make use of identifiers when the identifier system is not known." />
</base>
</type>
</constraint>
</extension>
<description value="A coded type for an identifier that can be used to determine which identifier to use for a specific purpose." />
</binding>
</mapping>
</mapping>
</element>
<definition value="Establishes the namespace for the value - that is, a URL that describes a set values that are unique." />
<requirements value="There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers." />
</base>
</type>
</example>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<definition value="The portion of the identifier typically relevant to the user and which is unique within the context of the system." />
<comment value="If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe." />
</base>
</type>
</example>
</constraint>
</mapping>
<map value="II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)" />
</mapping>
</mapping>
</element>
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<comment value="The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization." />
</base>
</type>
</constraint>
</mapping>
<map value="II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper" />
</mapping>
</mapping>
</element>
<definition value="Ovo je identifikator slučaja koji je dodjeljen slučaju u vanjskom informacijskom sustavu (sustavu koji koristi usluge komponente za Upravljanje slučajevima).\nVanjski sustav može dodjeliti i više ovakvih identifikatora no budući da se ovaj identifikator ne može smatrati globalno jedinstven prilikom [kreiranja novog slučaja](kreiraj_novi_slucaj.html) ili prilikom [kreiranja ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html), slučaju se također dodjeljuje globalni identifikator.\nOvaj tip identifikatora se može dodati, izmjeniti i obrisati iz podataka o slučaju i kroz [zahtjev za izmjenom podataka slučaja](izmjeni_podatke_slucaja.html)." />
<comment value="This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R4/resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number." />
<requirements value="Allows identification of the condition as it is known by various participating systems and in a way that remains consistent across servers." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
<comment value="Applications can assume that an identifier is permanent unless it explicitly says that it is temporary." />
<requirements value="Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers." />
</base>
</type>
</constraint>
</extension>
</binding>
</mapping>
</mapping>
</element>
<definition value="A coded type for the identifier that can be used to determine which identifier to use for a specific purpose." />
<comment value="This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type." />
<requirements value="Allows users to make use of identifiers when the identifier system is not known." />
</base>
</type>
</constraint>
</extension>
<description value="A coded type for an identifier that can be used to determine which identifier to use for a specific purpose." />
</binding>
</mapping>
</mapping>
</element>
<definition value="Establishes the namespace for the value - that is, a URL that describes a set values that are unique." />
<requirements value="There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers." />
</base>
</type>
<fixedUri value="http://fhir.cezih.hr/specifikacije/identifikatori/lokalni-identifikator-slucaja" />
</example>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<definition value="The portion of the identifier typically relevant to the user and which is unique within the context of the system." />
<comment value="If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe." />
</base>
</type>
</example>
</constraint>
</mapping>
<map value="II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)" />
</mapping>
</mapping>
</element>
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<comment value="The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization." />
</base>
</type>
</constraint>
</mapping>
<map value="II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper" />
</mapping>
</mapping>
</element>
<definition value="Klinički status slučaja se mijenja kroz poruke zahtjeva za upavljanje slučajevima kako je to opisano u [Slučajevima uporabe usluge za upravljanje slučajevima](slucajevi_uporabe.html). Status ne postavlja korisnik usluge već se on postavlja od strane same usluge za upravljanje slučajevima. Ukoliko korisnik pošalje neku vrijednost ona će biti zanemarena te će vrijednost ovog atributa biti postavljena na slijedeći način.\n\n[Prilikom kreiranja novog slučaja](kreiraj_novi_slucaj.html) dodljejuje se klinički startus "active".\n[Prilikom kreiranja ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) dodjeljuje se klinički status "recurrence"\n[Prilikom promjene statusa slučaja u remisija](promjeni_status_slucaja_u_remisija.html) dodjeljuje se klinički status "remission"\n[Prilikom promjene statusa slučaja u recidiv](promjeni_status_slucaja_u_recidiv.html) dodjeljuje se klinički status "relapse"\n[Prilikom zatvaranja slučaja](zatvori_slucaj.html) dodjeljuje se klinički status "resolved"\n[Prilikom brisanja slučaja](obrisi_slucaj.html) dodjeljuje se klinički status "inactive" s time da se vrijednost atributa "verificationStatus" postavlja u "entered-in-error"" />
<comment value="The data type is CodeableConcept because clinicalStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity." />
</base>
</type>
</constraint>
</extension>
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
<map value="Observation ACT\n.inboundRelationship[typeCode=COMP].source[classCode=OBS, code="clinicalStatus", moodCode=EVN].value" />
</mapping>
</element>
<definition value="Vrijednost potvrde slučaja se postavlja ovisno o poruci tj statusu zdravstvenog slučaja pacijenta. Vrijednost postavlja korisnik usluge a moguće vrijednosti su ovisno o poruci.\n\n[Prilikom kreiranja novog slučaja](kreiraj_novi_slucaj.html), [kreiranja ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i [prilikom promjene podataka o slučaju](izmjeni_podatke_slucaja.html) moguće su vrijednosti "unconfirmed", "provisional", "differential", "confirmed".\n[Prilikom zatvaranja slučaja](zatvori_slucaj.html) moguće su vrijednosti "confirmed", "refuted".\n[Prilikom brisanja slučaja](obrisi_slucaj.html) usluga automatski postavlja vrijednost ovog atributa u "entered-in-error" i zanemaruje vrijednost ovog atributa poslanog u poruci." />
<comment value="verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status.\nThe data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity." />
</base>
</type>
</constraint>
</extension>
<description value="The verification status to support or decline the clinical status of the condition or diagnosis." />
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
<map value="Observation ACT\n.inboundRelationship[typeCode=COMP].source[classCode=OBS, code="verificationStatus", moodCode=EVN].value" />
</mapping>
</mapping>
</element>
<comment value="The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts." />
</base>
</type>
</constraint>
</extension>
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="A subjective assessment of the severity of the condition as evaluated by the clinician." />
</base>
</type>
</constraint>
</extension>
<description value="A subjective assessment of the severity of the condition as evaluated by the clinician." />
</binding>
</mapping>
</mapping>
</mapping>
<map value="Can be pre/post-coordinated into value. Or ./inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="severity"].value" />
</mapping>
</mapping>
</element>
</base>
</type>
</constraint>
</binding>
</mapping>
</mapping>
<map value="code 246090004 |Associated finding| (< 404684003 |Clinical finding| MINUS\n<< 420134006 |Propensity to adverse reactions| MINUS \n<< 473010000 |Hypersensitivity condition| MINUS \n<< 79899007 |Drug interaction| MINUS\n<< 69449002 |Drug action| MINUS \n<< 441742003 |Evaluation finding| MINUS \n<< 307824009 |Administrative status| MINUS \n<< 385356007 |Tumor stage finding|) \nOR < 413350009 |Finding with explicit context|\nOR < 272379006 |Event|" />
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<comment value="Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite](http://hl7.org/fhir/R4/extension-bodysite.html). May be a summary code, or a reference to a very precise definition of the location, or both." />
</base>
</type>
</constraint>
</extension>
</binding>
</mapping>
</mapping>
</mapping>
</element>
</base>
</type>
</constraint>
<human value="Ako se pacijent referencira sa identifikatorom potrebno je specificirati i tip resursa "Patient"" />
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Koristi se logička referenca (identifikator posjete koji je usluga Upravljanje posjetama dodjelila slučaju prilikom kreiiranja nove posjete)." />
<comment value="This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. This record indicates the encounter this particular record is associated with. In the case of a "new" diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first "known"." />
</base>
</type>
</constraint>
<human value="Ako se posjeta u kojoj je kreiran slučaj referencira sa identifikatorom potrebno je specificirati i tip resursa "Encounter"" />
</constraint>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Ovo vrijeme ne mora biti jednako vremenu kada su informacije o slučaju zabilježene. Moguće je kreirati podatke o slučaju za slučajeve koji su se pojavili u prošlosti. Može se koristiti datum (puni ili samo godina) ili starost pacijenta (npr u dobi od 40 godina).\nOvaj podatak se može specificirati i mijenjati samo kroz slijedeće poruke. \n\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i [Promjena podataka o slučaju](izmjeni_podatke_slucaja.html).\n\nUkoliko se pošalje u bilo kojoj drugoj poruci biti će zanemaren." />
<comment value="Age is generally used when the patient reports an age at which the Condition began to occur." />
</base>
</type>
</type>
</type>
</type>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
<map value=".effectiveTime.low or .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="age at onset"].value" />
</mapping>
</element>
<definition value="Moguće je kreirati podatke o slučaju za slučajeve koji su se pojavili u prošlosti i koji su zatvoreni u prošlosti. Može se koristiti datum (puni ili samo godina) ili starost pacijenta (npr u dobi od 40 godina).\n\nOvaj podatak se može specificirati i mijenjati samo kroz slijedeće poruke. \n\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i [Promjena podataka o slučaju](izmjeni_podatke_slucaja.html).\n\nUkoliko se pošalje u bilo kojoj drugoj poruci biti će zanemaren." />
<comment value="There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated." />
</base>
</type>
</type>
</type>
</type>
</type>
</constraint>
</mapping>
<map value=".effectiveTime.high or .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="age at remission"].value or .inboundRelationship[typeCode=SUBJ]source[classCode=CONC, moodCode=EVN].status=completed" />
</mapping>
</element>
<definition value="Ovo vrijeme dodjeljuje sustav. Ukoliko korisnik pošalje ovaj podatak u bio kojoj poruci biti će zanemaren i koristit će se vrijeme kada je [novi](kreiraj_novi_slucaj.html) ili [ponovljeni slučaj](kreiraj_ponovljeni_slucaj.html) kreiran." />
</base>
</type>
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Ovaj podatak se može specificirati samo u porukama\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i jednak je autoru poruke.\n\nU svim ostalim porukama podatak će se zanemariti." />
</base>
</type>
</constraint>
<human value="Ako se zdravstveni djelatnik referencira sa identifikatorom potrebno je specificirati tip resursa "Practitioner"" />
</constraint>
</mapping>
</mapping>
</element>
<definition value="Ovaj podatak se može specificirati samo u porukama\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html), [Promjena podataka o slučaju](izmjeni_podatke_slucaja.html) .\n\nU svim ostalim porukama podatak će se zanemariti." />
</base>
</type>
</constraint>
<human value="Ako se zdravstveni djelatnik referencira sa identifikatorom potrebno je specificirati tip resursa "Practitioner"" />
</constraint>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Clinical stage or grade of a condition. May include formal severity assessments." />
</base>
</type>
</constraint>
</constraint>
<map value="./inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="stage/grade"]" />
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
<definition value="May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself)." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
<requirements value="Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension)." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
<definition value="A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific." />
</base>
</type>
</constraint>
</extension>
</binding>
</mapping>
</mapping>
</mapping>
</element>
<definition value="Reference to a formal record of the evidence on which the staging assessment is based." />
</base>
</type>
</constraint>
</mapping>
</element>
</base>
</type>
</constraint>
</extension>
<description value="Codes describing the kind of condition staging (e.g. clinical or pathological)." />
</binding>
<map value="./inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="stage type"]" />
</mapping>
</element>
<definition value="Supporting evidence / manifestations that are the basis of the Condition's verification status, such as evidence that confirmed or refuted the condition." />
<comment value="The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
<definition value="May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself)." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
<requirements value="Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension)." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
</base>
</type>
</constraint>
</extension>
</binding>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</base>
</type>
</constraint>
</mapping>
</mapping>
</element>
<definition value="Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis." />
</base>
</type>
</constraint>
</mapping>
</mapping>
<map value=".inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="annotation"].value" />
</mapping>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
</base>
</type>
</constraint>
</constraint>
</element>
<definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." />
</base>
</extension>
</type>
</mapping>
</element>
</discriminator>
</slicing>
<definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." />
<comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." />
</base>
</type>
</constraint>
</constraint>
</mapping>
</element>
<comment value="The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension." />
</base>
</extension>
</type>
</mapping>
</element>
<definition value="Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list)." />
</base>
</type>
</constraint>
</binding>
</mapping>
</element>
<comment value="Organization is used when there's no need for specific attribution as to who made the comment." />
</base>
</type>
</type>
</constraint>
</mapping>
</mapping>
</element>
</base>
</type>
</constraint>
</mapping>
</mapping>
</element>
</base>
</type>
</constraint>
</mapping>
</mapping>
</element>
</snapshot>
</element>
</slicing>
</element>
<definition value="Ekstenzija definira vezu i tip veze prema drugom slučaju zdravlja (Health Issue). Predmetni slučaj može biti komplikacija, komorbiditet, zamjena itd. slučaja prema kojem ima vezu (referencu)." />
</type>
</element>
</discriminator>
</slicing>
</element>
<definition value="Ovaj identifikator dodjeljuje usluga "Upravljanje slučajevima" prilikom kreiranja novog slučaja ili kreiranja ponovljenog slučaja. Ovaj identifikator se smatra globalno jedinstven i nemogu postojati dva slučaja sa istim identifikatorom ovog tipa." />
</element>
</element>
<definition value="Ovo je identifikator slučaja koji je dodjeljen slučaju u vanjskom informacijskom sustavu (sustavu koji koristi usluge komponente za Upravljanje slučajevima).\nVanjski sustav može dodjeliti i više ovakvih identifikatora no budući da se ovaj identifikator ne može smatrati globalno jedinstven prilikom [kreiranja novog slučaja](kreiraj_novi_slucaj.html) ili prilikom [kreiranja ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html), slučaju se također dodjeljuje globalni identifikator.\nOvaj tip identifikatora se može dodati, izmjeniti i obrisati iz podataka o slučaju i kroz [zahtjev za izmjenom podataka slučaja](izmjeni_podatke_slucaja.html)." />
</element>
<fixedUri value="http://fhir.cezih.hr/specifikacije/identifikatori/lokalni-identifikator-slucaja" />
</element>
<definition value="Klinički status slučaja se mijenja kroz poruke zahtjeva za upavljanje slučajevima kako je to opisano u [Slučajevima uporabe usluge za upravljanje slučajevima](slucajevi_uporabe.html). Status ne postavlja korisnik usluge već se on postavlja od strane same usluge za upravljanje slučajevima. Ukoliko korisnik pošalje neku vrijednost ona će biti zanemarena te će vrijednost ovog atributa biti postavljena na slijedeći način.\n\n[Prilikom kreiranja novog slučaja](kreiraj_novi_slucaj.html) dodljejuje se klinički startus "active".\n[Prilikom kreiranja ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) dodjeljuje se klinički status "recurrence"\n[Prilikom promjene statusa slučaja u remisija](promjeni_status_slucaja_u_remisija.html) dodjeljuje se klinički status "remission"\n[Prilikom promjene statusa slučaja u recidiv](promjeni_status_slucaja_u_recidiv.html) dodjeljuje se klinički status "relapse"\n[Prilikom zatvaranja slučaja](zatvori_slucaj.html) dodjeljuje se klinički status "resolved"\n[Prilikom brisanja slučaja](obrisi_slucaj.html) dodjeljuje se klinički status "inactive" s time da se vrijednost atributa "verificationStatus" postavlja u "entered-in-error"" />
</element>
<definition value="Vrijednost potvrde slučaja se postavlja ovisno o poruci tj statusu zdravstvenog slučaja pacijenta. Vrijednost postavlja korisnik usluge a moguće vrijednosti su ovisno o poruci.\n\n[Prilikom kreiranja novog slučaja](kreiraj_novi_slucaj.html), [kreiranja ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i [prilikom promjene podataka o slučaju](izmjeni_podatke_slucaja.html) moguće su vrijednosti "unconfirmed", "provisional", "differential", "confirmed".\n[Prilikom zatvaranja slučaja](zatvori_slucaj.html) moguće su vrijednosti "confirmed", "refuted".\n[Prilikom brisanja slučaja](obrisi_slucaj.html) usluga automatski postavlja vrijednost ovog atributa u "entered-in-error" i zanemaruje vrijednost ovog atributa poslanog u poruci." />
</element>
</element>
</element>
</binding>
</element>
</element>
</type>
<human value="Ako se pacijent referencira sa identifikatorom potrebno je specificirati i tip resursa "Patient"" />
</constraint>
</element>
<definition value="Koristi se logička referenca (identifikator posjete koji je usluga Upravljanje posjetama dodjelila slučaju prilikom kreiiranja nove posjete)." />
</type>
<human value="Ako se posjeta u kojoj je kreiran slučaj referencira sa identifikatorom potrebno je specificirati i tip resursa "Encounter"" />
</constraint>
</element>
<definition value="Ovo vrijeme ne mora biti jednako vremenu kada su informacije o slučaju zabilježene. Moguće je kreirati podatke o slučaju za slučajeve koji su se pojavili u prošlosti. Može se koristiti datum (puni ili samo godina) ili starost pacijenta (npr u dobi od 40 godina).\nOvaj podatak se može specificirati i mijenjati samo kroz slijedeće poruke. \n\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i [Promjena podataka o slučaju](izmjeni_podatke_slucaja.html).\n\nUkoliko se pošalje u bilo kojoj drugoj poruci biti će zanemaren." />
</element>
<definition value="Moguće je kreirati podatke o slučaju za slučajeve koji su se pojavili u prošlosti i koji su zatvoreni u prošlosti. Može se koristiti datum (puni ili samo godina) ili starost pacijenta (npr u dobi od 40 godina).\n\nOvaj podatak se može specificirati i mijenjati samo kroz slijedeće poruke. \n\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i [Promjena podataka o slučaju](izmjeni_podatke_slucaja.html).\n\nUkoliko se pošalje u bilo kojoj drugoj poruci biti će zanemaren." />
</element>
<definition value="Ovo vrijeme dodjeljuje sustav. Ukoliko korisnik pošalje ovaj podatak u bio kojoj poruci biti će zanemaren i koristit će se vrijeme kada je [novi](kreiraj_novi_slucaj.html) ili [ponovljeni slučaj](kreiraj_ponovljeni_slucaj.html) kreiran." />
</element>
<definition value="Ovaj podatak se može specificirati samo u porukama\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i jednak je autoru poruke.\n\nU svim ostalim porukama podatak će se zanemariti." />
</type>
<human value="Ako se zdravstveni djelatnik referencira sa identifikatorom potrebno je specificirati tip resursa "Practitioner"" />
</constraint>
</element>
<definition value="Ovaj podatak se može specificirati samo u porukama\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html), [Promjena podataka o slučaju](izmjeni_podatke_slucaja.html) .\n\nU svim ostalim porukama podatak će se zanemariti." />
</type>
<human value="Ako se zdravstveni djelatnik referencira sa identifikatorom potrebno je specificirati tip resursa "Practitioner"" />
</constraint>
</element>
</element>
</type>
</element>
</type>
</binding>
</element>
</differential>
</StructureDefinition>
{
},
--- We have skipped the narrative for better readability of the resource ---
},
{
]
}
],
"description": "Podatci o zdravstvenom slučaju.\n\nKoncept Slučaja predstavlja određeni zdravstveni problem ili stanje pacijenta u određenom trenutku u vremenu. Slučaj je definiran sa tri osnovna atributa: dijagnoza, vrijeme početka i završetka problema odnosno stanja te status slučaja. \n\nDomenski model podataka o Slučaju prikazan je na slijedećoj slici.\n\n<table>\n<tr><td><img style=\"max-width:100%\" src=\"HI Domain Model.jpg\" /></td></tr>\n<tr><td>Slika 1 - Domenski model podataka o slučaju</td></tr>\n</table>\nKako je prikazano na slici 1 podatci o slučaju se sastoje od \n* jedinstvenog identifikatora slučaja kojeg dodjeljuje ova usluga prilikom kreiranja slučaja (identifier)\n* datum završetka slučaja (abatement date)\n* datum početka slučaja (onset date)\n* datum kada je slučaj zabilježen (recorded date)\n* status slučaja (clinical status)\n* status verifikacije slučaja (verification status)\n* dijagnoza (identification of HI)\n* vezani slučaj (related)\n* posjeta u kojoj je identificiran slučaj (encounter)\n* pacijent (subject)\n* liječnik koji je identificirao slučaj (asserter)\n* liječnik koji je zabilježio slučaj (recorder)\n\nNa slijedećoj slici su prikazana stanja slučaja (clinical status).\n\n<table>\n<tr><td><img style=\"max-width:100%\" src=\"HI State Model.jpg\" /></td></tr>\n<tr><td>Slika 2 - Model stanja</td></tr>\n</table>",
{
],
}
],
{
},
{
},
{
},
{
},
{
},
{
}
],
{
"definition": "A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.",
},
{
{
},
{
"valueMarkdown": "Most systems will expect a clinicalStatus to be valued for problem-list-items that are managed over time, but might not need a clinicalStatus for point in time encounter-diagnosis."
}
],
"human": "Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item",
"expression": "clinicalStatus.exists() or verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code = 'entered-in-error').exists() or category.select($this='problem-list-item').empty()",
"xpath": "exists(f:clinicalStatus) or exists(f:verificationStatus/f:coding/f:code/@value='entered-in-error') or not(exists(category[@value='problem-list-item']))",
},
{
"human": "If condition is abated, then clinicalStatus must be either inactive, resolved, or remission",
"expression": "abatement.empty() or clinicalStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-clinical' and (code='resolved' or code='remission' or code='inactive')).exists()",
"xpath": "not(exists(*[starts-with(local-name(.), 'abatement')])) or exists(f:clinicalStatus/f:coding[f:system/@value='http://terminology.hl7.org/CodeSystem/condition-clinical' and f:code/@value=('resolved', 'remission', 'inactive')])",
},
{
"human": "Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error",
"expression": "verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code='entered-in-error').empty() or clinicalStatus.empty()",
"xpath": "not(exists(f:verificationStatus/f:coding[f:system/@value='http://terminology.hl7.org/CodeSystem/condition-ver-status' and f:code/@value='entered-in-error'])) or not(exists(f:clinicalStatus))",
},
{
},
{
"human": "If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource",
"expression": "contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()",
"xpath": "not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))",
},
{
"human": "If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated",
"xpath": "not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))",
},
{
},
{
{
},
{
"valueMarkdown": "When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time."
}
],
}
],
{
},
{
},
{
"map": "< 243796009 |Situation with explicit context| : 246090004 |Associated finding| = ( ( < 404684003 |Clinical finding| MINUS ( << 420134006 |Propensity to adverse reactions| OR << 473010000 |Hypersensitivity condition| OR << 79899007 |Drug interaction| OR << 69449002 |Drug action| OR << 441742003 |Evaluation finding| OR << 307824009 |Administrative status| OR << 385356007 |Tumor stage finding|)) OR < 272379006 |Event|)"
},
{
},
{
}
]
},
{
"definition": "The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.",
"comment": "The only time that a resource does not have an id is when it is being submitted to the server using a create operation.",
},
{
{
}
],
}
],
},
{
"definition": "The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.",
},
],
{
}
],
},
{
"definition": "A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.",
"comment": "Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.",
},
],
{
}
],
},
{
"comment": "Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).",
},
],
{
}
],
{
},
{
}
],
}
},
{
"definition": "A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it \"clinically safe\" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.",
"comment": "Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a \"text blob\" or where text is additionally entered raw or narrated and encoded information is added later.",
"narrative",
"html",
"xhtml",
"display"
],
},
],
{
}
],
]
},
{
"definition": "These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.",
"comment": "This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.",
"inline resources",
"anonymous resources",
"contained resources"
],
},
],
]
},
{
},
},
],
{
},
{
}
],
},
{
"definition": "Ekstenzija definira vezu i tip veze prema drugom slučaju zdravlja (Health Issue). Predmetni slučaj može biti komplikacija, komorbiditet, zamjena itd. slučaja prema kojem ima vezu (referencu).",
},
],
"ele-1"
],
{
},
{
}
],
},
{
"definition": "May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"requirements": "Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).",
"extensions",
"user content"
],
},
],
{
},
{
}
],
]
},
{
},
"definition": "Business identifiers assigned to this condition by the performer or other systems which remain constant as the resource is updated and propagates from server to server.",
"comment": "This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R4/resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.",
"requirements": "Allows identification of the condition as it is known by various participating systems and in a way that remains consistent across servers.",
},
],
{
}
],
{
},
{
},
{
}
]
},
{
"definition": "Ovaj identifikator dodjeljuje usluga \"Upravljanje slučajevima\" prilikom kreiranja novog slučaja ili kreiranja ponovljenog slučaja. Ovaj identifikator se smatra globalno jedinstven i nemogu postojati dva slučaja sa istim identifikatorom ovog tipa.",
"comment": "This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R4/resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.",
"requirements": "Allows identification of the condition as it is known by various participating systems and in a way that remains consistent across servers.",
},
],
{
}
],
{
},
{
},
{
}
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
{
},
{
}
],
]
},
{
"comment": "Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.",
"requirements": "Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.",
},
],
{
}
],
{
}
],
},
]
},
{
"definition": "A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.",
"comment": "This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.",
},
],
{
}
],
{
}
],
"description": "A coded type for an identifier that can be used to determine which identifier to use for a specific purpose."
},
{
},
{
}
]
},
{
"definition": "Establishes the namespace for the value - that is, a URL that describes a set values that are unique.",
"requirements": "There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.",
},
],
],
{
}
],
{
},
{
},
{
}
]
},
{
"definition": "The portion of the identifier typically relevant to the user and which is unique within the context of the system.",
"comment": "If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.",
},
],
],
{
}
],
{
},
{
},
{
}
]
},
{
},
],
{
}
],
{
},
{
},
{
}
]
},
{
"comment": "The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.",
},
],
{
}
],
{
},
{
"map": "II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper"
},
{
}
]
},
{
"definition": "Ovo je identifikator slučaja koji je dodjeljen slučaju u vanjskom informacijskom sustavu (sustavu koji koristi usluge komponente za Upravljanje slučajevima).\nVanjski sustav može dodjeliti i više ovakvih identifikatora no budući da se ovaj identifikator ne može smatrati globalno jedinstven prilikom [kreiranja novog slučaja](kreiraj_novi_slucaj.html) ili prilikom [kreiranja ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html), slučaju se također dodjeljuje globalni identifikator.\nOvaj tip identifikatora se može dodati, izmjeniti i obrisati iz podataka o slučaju i kroz [zahtjev za izmjenom podataka slučaja](izmjeni_podatke_slucaja.html).",
"comment": "This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R4/resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.",
"requirements": "Allows identification of the condition as it is known by various participating systems and in a way that remains consistent across servers.",
},
],
{
}
],
{
},
{
},
{
}
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
{
},
{
}
],
]
},
{
"comment": "Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.",
"requirements": "Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.",
},
],
{
}
],
{
}
],
},
]
},
{
"definition": "A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.",
"comment": "This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.",
},
],
{
}
],
{
}
],
"description": "A coded type for an identifier that can be used to determine which identifier to use for a specific purpose."
},
{
},
{
}
]
},
{
"definition": "Establishes the namespace for the value - that is, a URL that describes a set values that are unique.",
"requirements": "There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.",
},
],
],
{
}
],
{
},
{
},
{
}
]
},
{
"definition": "The portion of the identifier typically relevant to the user and which is unique within the context of the system.",
"comment": "If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.",
},
],
],
{
}
],
{
},
{
},
{
}
]
},
{
},
],
{
}
],
{
},
{
},
{
}
]
},
{
"comment": "The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.",
},
],
{
}
],
{
},
{
"map": "II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper"
},
{
}
]
},
{
"definition": "Klinički status slučaja se mijenja kroz poruke zahtjeva za upavljanje slučajevima kako je to opisano u [Slučajevima uporabe usluge za upravljanje slučajevima](slucajevi_uporabe.html). Status ne postavlja korisnik usluge već se on postavlja od strane same usluge za upravljanje slučajevima. Ukoliko korisnik pošalje neku vrijednost ona će biti zanemarena te će vrijednost ovog atributa biti postavljena na slijedeći način.\n\n[Prilikom kreiranja novog slučaja](kreiraj_novi_slucaj.html) dodljejuje se klinički startus \"active\".\n[Prilikom kreiranja ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) dodjeljuje se klinički status \"recurrence\"\n[Prilikom promjene statusa slučaja u remisija](promjeni_status_slucaja_u_remisija.html) dodjeljuje se klinički status \"remission\"\n[Prilikom promjene statusa slučaja u recidiv](promjeni_status_slucaja_u_recidiv.html) dodjeljuje se klinički status \"relapse\"\n[Prilikom zatvaranja slučaja](zatvori_slucaj.html) dodjeljuje se klinički status \"resolved\"\n[Prilikom brisanja slučaja](obrisi_slucaj.html) dodjeljuje se klinički status \"inactive\" s time da se vrijednost atributa \"verificationStatus\" postavlja u \"entered-in-error\"",
"comment": "The data type is CodeableConcept because clinicalStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.",
},
],
"con-3",
"con-4",
"con-5"
],
{
}
],
{
}
],
},
{
},
{
},
{
},
{
},
{
"map": "Observation ACT\n.inboundRelationship[typeCode=COMP].source[classCode=OBS, code=\"clinicalStatus\", moodCode=EVN].value"
}
]
},
{
"definition": "Vrijednost potvrde slučaja se postavlja ovisno o poruci tj statusu zdravstvenog slučaja pacijenta. Vrijednost postavlja korisnik usluge a moguće vrijednosti su ovisno o poruci.\n\n[Prilikom kreiranja novog slučaja](kreiraj_novi_slucaj.html), [kreiranja ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i [prilikom promjene podataka o slučaju](izmjeni_podatke_slucaja.html) moguće su vrijednosti \"unconfirmed\", \"provisional\", \"differential\", \"confirmed\".\n[Prilikom zatvaranja slučaja](zatvori_slucaj.html) moguće su vrijednosti \"confirmed\", \"refuted\".\n[Prilikom brisanja slučaja](obrisi_slucaj.html) usluga automatski postavlja vrijednost ovog atributa u \"entered-in-error\" i zanemaruje vrijednost ovog atributa poslanog u poruci.",
"comment": "verificationStatus is not required. For example, when a patient has abdominal pain in the ED, there is not likely going to be a verification status.\nThe data type is CodeableConcept because verificationStatus has some clinical judgment involved, such that there might need to be more specificity than the required FHIR value set allows. For example, a SNOMED coding might allow for additional specificity.",
},
],
"con-3",
"con-5"
],
{
}
],
{
}
],
"description": "The verification status to support or decline the clinical status of the condition or diagnosis."
},
{
},
{
},
{
},
{
},
{
"map": "Observation ACT\n.inboundRelationship[typeCode=COMP].source[classCode=OBS, code=\"verificationStatus\", moodCode=EVN].value"
},
{
}
]
},
{
"comment": "The categorization is often highly contextual and may appear poorly differentiated or not very useful in other contexts.",
},
],
{
}
],
{
}
],
},
{
},
{
},
{
},
{
}
]
},
{
"definition": "A subjective assessment of the severity of the condition as evaluated by the clinician.",
},
],
{
}
],
{
}
],
"description": "A subjective assessment of the severity of the condition as evaluated by the clinician."
},
{
},
{
},
{
},
{
"map": "Can be pre/post-coordinated into value. Or ./inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code=\"severity\"].value"
},
{
}
]
},
{
"type"
],
},
],
{
}
],
},
{
},
{
},
{
"map": "code 246090004 |Associated finding| (< 404684003 |Clinical finding| MINUS\n<< 420134006 |Propensity to adverse reactions| MINUS \n<< 473010000 |Hypersensitivity condition| MINUS \n<< 79899007 |Drug interaction| MINUS\n<< 69449002 |Drug action| MINUS \n<< 441742003 |Evaluation finding| MINUS \n<< 307824009 |Administrative status| MINUS \n<< 385356007 |Tumor stage finding|) \nOR < 413350009 |Finding with explicit context|\nOR < 272379006 |Event|"
},
{
},
{
},
{
}
]
},
{
"comment": "Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite](http://hl7.org/fhir/R4/extension-bodysite.html). May be a summary code, or a reference to a very precise definition of the location, or both.",
},
],
{
}
],
{
}
],
},
{
},
{
},
{
}
]
},
{
"patient"
],
},
],
{
},
{
"human": "Ako se pacijent referencira sa identifikatorom potrebno je specificirati i tip resursa \"Patient\"",
}
],
{
},
{
},
{
},
{
},
{
}
]
},
{
"definition": "Koristi se logička referenca (identifikator posjete koji je usluga Upravljanje posjetama dodjelila slučaju prilikom kreiiranja nove posjete).",
"comment": "This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. This record indicates the encounter this particular record is associated with. In the case of a \"new\" diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first \"known\".",
},
],
{
},
{
"human": "Ako se posjeta u kojoj je kreiran slučaj referencira sa identifikatorom potrebno je specificirati i tip resursa \"Encounter\"",
}
],
{
},
{
},
{
},
{
}
]
},
{
"definition": "Ovo vrijeme ne mora biti jednako vremenu kada su informacije o slučaju zabilježene. Moguće je kreirati podatke o slučaju za slučajeve koji su se pojavili u prošlosti. Može se koristiti datum (puni ili samo godina) ili starost pacijenta (npr u dobi od 40 godina).\nOvaj podatak se može specificirati i mijenjati samo kroz slijedeće poruke. \n\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i [Promjena podataka o slučaju](izmjeni_podatke_slucaja.html).\n\nUkoliko se pošalje u bilo kojoj drugoj poruci biti će zanemaren.",
"comment": "Age is generally used when the patient reports an age at which the Condition began to occur.",
},
{
},
{
},
{
},
{
},
{
}
],
{
}
],
{
},
{
},
{
},
{
"map": ".effectiveTime.low or .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code=\"age at onset\"].value"
}
]
},
{
"definition": "Moguće je kreirati podatke o slučaju za slučajeve koji su se pojavili u prošlosti i koji su zatvoreni u prošlosti. Može se koristiti datum (puni ili samo godina) ili starost pacijenta (npr u dobi od 40 godina).\n\nOvaj podatak se može specificirati i mijenjati samo kroz slijedeće poruke. \n\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i [Promjena podataka o slučaju](izmjeni_podatke_slucaja.html).\n\nUkoliko se pošalje u bilo kojoj drugoj poruci biti će zanemaren.",
"comment": "There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated.",
},
{
},
{
},
{
},
{
},
{
}
],
"con-4"
],
{
}
],
{
},
{
"map": ".effectiveTime.high or .inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code=\"age at remission\"].value or .inboundRelationship[typeCode=SUBJ]source[classCode=CONC, moodCode=EVN].status=completed"
}
]
},
{
"definition": "Ovo vrijeme dodjeljuje sustav. Ukoliko korisnik pošalje ovaj podatak u bio kojoj poruci biti će zanemaren i koristit će se vrijeme kada je [novi](kreiraj_novi_slucaj.html) ili [ponovljeni slučaj](kreiraj_ponovljeni_slucaj.html) kreiran.",
},
],
{
}
],
{
},
{
},
{
}
]
},
{
"definition": "Ovaj podatak se može specificirati samo u porukama\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i jednak je autoru poruke.\n\nU svim ostalim porukama podatak će se zanemariti.",
},
],
{
},
{
"human": "Ako se zdravstveni djelatnik referencira sa identifikatorom potrebno je specificirati tip resursa \"Practitioner\"",
}
],
{
},
{
}
]
},
{
"definition": "Ovaj podatak se može specificirati samo u porukama\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html), [Promjena podataka o slučaju](izmjeni_podatke_slucaja.html) .\n\nU svim ostalim porukama podatak će se zanemariti.",
},
],
{
},
{
"human": "Ako se zdravstveni djelatnik referencira sa identifikatorom potrebno je specificirati tip resursa \"Practitioner\"",
}
],
{
},
{
},
{
}
]
},
{
},
],
{
},
{
}
],
{
"map": "./inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code=\"stage/grade\"]"
}
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
{
},
{
}
],
]
},
{
"definition": "May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"requirements": "Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).",
"extensions",
"user content",
"modifiers"
],
},
],
{
},
{
}
],
]
},
{
"definition": "A simple summary of the stage such as \"Stage 3\". The determination of the stage is disease-specific.",
},
],
"con-1"
],
{
}
],
{
}
],
},
{
},
{
},
{
}
]
},
{
"definition": "Reference to a formal record of the evidence on which the staging assessment is based.",
},
],
"con-1"
],
{
}
],
]
},
{
},
],
{
}
],
{
}
],
},
{
"map": "./inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code=\"stage type\"]"
}
]
},
{
"definition": "Supporting evidence / manifestations that are the basis of the Condition's verification status, such as evidence that confirmed or refuted the condition.",
"comment": "The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both.",
},
],
{
},
{
}
],
{
}
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
{
},
{
}
],
]
},
{
"definition": "May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.\n\nModifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"requirements": "Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).",
"extensions",
"user content",
"modifiers"
],
},
],
{
},
{
}
],
]
},
{
},
],
"con-2"
],
{
}
],
{
}
],
},
{
},
{
},
{
},
{
}
]
},
{
},
],
"con-2"
],
{
}
],
]
},
{
"definition": "Additional information about the Condition. This is a general notes/comments entry for description of the Condition, its diagnosis and prognosis.",
},
],
{
}
],
{
},
{
},
{
"map": ".inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code=\"annotation\"].value"
}
]
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
},
],
{
},
{
}
],
},
{
"xmlAttr"
],
"definition": "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
},
{
{
}
],
}
],
]
},
{
],
},
"definition": "May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.",
"comment": "There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"extensions",
"user content"
],
},
],
{
},
{
}
],
]
},
{
"xmlAttr"
],
"comment": "The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.",
},
{
{
}
],
}
],
]
},
{
"definition": "Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).",
},
],
{
}
],
},
]
},
{
"comment": "Organization is used when there's no need for specific attribution as to who made the comment.",
},
],
{
}
],
{
},
{
}
]
},
{
},
],
{
}
],
]
},
{
},
],
{
}
],
]
}
]
},
{
},
{
}
},
{
"definition": "Ekstenzija definira vezu i tip veze prema drugom slučaju zdravlja (Health Issue). Predmetni slučaj može biti komplikacija, komorbiditet, zamjena itd. slučaja prema kojem ima vezu (referencu).",
],
},
{
},
},
{
"definition": "Ovaj identifikator dodjeljuje usluga \"Upravljanje slučajevima\" prilikom kreiranja novog slučaja ili kreiranja ponovljenog slučaja. Ovaj identifikator se smatra globalno jedinstven i nemogu postojati dva slučaja sa istim identifikatorom ovog tipa.",
},
{
},
{
"definition": "Ovo je identifikator slučaja koji je dodjeljen slučaju u vanjskom informacijskom sustavu (sustavu koji koristi usluge komponente za Upravljanje slučajevima).\nVanjski sustav može dodjeliti i više ovakvih identifikatora no budući da se ovaj identifikator ne može smatrati globalno jedinstven prilikom [kreiranja novog slučaja](kreiraj_novi_slucaj.html) ili prilikom [kreiranja ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html), slučaju se također dodjeljuje globalni identifikator.\nOvaj tip identifikatora se može dodati, izmjeniti i obrisati iz podataka o slučaju i kroz [zahtjev za izmjenom podataka slučaja](izmjeni_podatke_slucaja.html).",
},
{
},
{
"definition": "Klinički status slučaja se mijenja kroz poruke zahtjeva za upavljanje slučajevima kako je to opisano u [Slučajevima uporabe usluge za upravljanje slučajevima](slucajevi_uporabe.html). Status ne postavlja korisnik usluge već se on postavlja od strane same usluge za upravljanje slučajevima. Ukoliko korisnik pošalje neku vrijednost ona će biti zanemarena te će vrijednost ovog atributa biti postavljena na slijedeći način.\n\n[Prilikom kreiranja novog slučaja](kreiraj_novi_slucaj.html) dodljejuje se klinički startus \"active\".\n[Prilikom kreiranja ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) dodjeljuje se klinički status \"recurrence\"\n[Prilikom promjene statusa slučaja u remisija](promjeni_status_slucaja_u_remisija.html) dodjeljuje se klinički status \"remission\"\n[Prilikom promjene statusa slučaja u recidiv](promjeni_status_slucaja_u_recidiv.html) dodjeljuje se klinički status \"relapse\"\n[Prilikom zatvaranja slučaja](zatvori_slucaj.html) dodjeljuje se klinički status \"resolved\"\n[Prilikom brisanja slučaja](obrisi_slucaj.html) dodjeljuje se klinički status \"inactive\" s time da se vrijednost atributa \"verificationStatus\" postavlja u \"entered-in-error\"",
},
{
"definition": "Vrijednost potvrde slučaja se postavlja ovisno o poruci tj statusu zdravstvenog slučaja pacijenta. Vrijednost postavlja korisnik usluge a moguće vrijednosti su ovisno o poruci.\n\n[Prilikom kreiranja novog slučaja](kreiraj_novi_slucaj.html), [kreiranja ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i [prilikom promjene podataka o slučaju](izmjeni_podatke_slucaja.html) moguće su vrijednosti \"unconfirmed\", \"provisional\", \"differential\", \"confirmed\".\n[Prilikom zatvaranja slučaja](zatvori_slucaj.html) moguće su vrijednosti \"confirmed\", \"refuted\".\n[Prilikom brisanja slučaja](obrisi_slucaj.html) usluga automatski postavlja vrijednost ovog atributa u \"entered-in-error\" i zanemaruje vrijednost ovog atributa poslanog u poruci.",
},
{
},
{
},
{
}
},
{
},
{
],
{
"human": "Ako se pacijent referencira sa identifikatorom potrebno je specificirati i tip resursa \"Patient\"",
}
],
},
{
"definition": "Koristi se logička referenca (identifikator posjete koji je usluga Upravljanje posjetama dodjelila slučaju prilikom kreiiranja nove posjete).",
],
{
"human": "Ako se posjeta u kojoj je kreiran slučaj referencira sa identifikatorom potrebno je specificirati i tip resursa \"Encounter\"",
}
],
},
{
"definition": "Ovo vrijeme ne mora biti jednako vremenu kada su informacije o slučaju zabilježene. Moguće je kreirati podatke o slučaju za slučajeve koji su se pojavili u prošlosti. Može se koristiti datum (puni ili samo godina) ili starost pacijenta (npr u dobi od 40 godina).\nOvaj podatak se može specificirati i mijenjati samo kroz slijedeće poruke. \n\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i [Promjena podataka o slučaju](izmjeni_podatke_slucaja.html).\n\nUkoliko se pošalje u bilo kojoj drugoj poruci biti će zanemaren.",
},
{
"definition": "Moguće je kreirati podatke o slučaju za slučajeve koji su se pojavili u prošlosti i koji su zatvoreni u prošlosti. Može se koristiti datum (puni ili samo godina) ili starost pacijenta (npr u dobi od 40 godina).\n\nOvaj podatak se može specificirati i mijenjati samo kroz slijedeće poruke. \n\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i [Promjena podataka o slučaju](izmjeni_podatke_slucaja.html).\n\nUkoliko se pošalje u bilo kojoj drugoj poruci biti će zanemaren.",
},
{
"definition": "Ovo vrijeme dodjeljuje sustav. Ukoliko korisnik pošalje ovaj podatak u bio kojoj poruci biti će zanemaren i koristit će se vrijeme kada je [novi](kreiraj_novi_slucaj.html) ili [ponovljeni slučaj](kreiraj_ponovljeni_slucaj.html) kreiran.",
},
{
"definition": "Ovaj podatak se može specificirati samo u porukama\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html) i jednak je autoru poruke.\n\nU svim ostalim porukama podatak će se zanemariti.",
],
{
"human": "Ako se zdravstveni djelatnik referencira sa identifikatorom potrebno je specificirati tip resursa \"Practitioner\"",
}
],
},
{
"definition": "Ovaj podatak se može specificirati samo u porukama\n[Kreiranje novog slučaja](kreiraj_novi_slucaj.html), [Kreiranje ponovljenog slučaja](kreiraj_ponovljeni_slucaj.html), [Promjena podataka o slučaju](izmjeni_podatke_slucaja.html) .\n\nU svim ostalim porukama podatak će se zanemariti.",
],
{
"human": "Ako se zdravstveni djelatnik referencira sa identifikatorom potrebno je specificirati tip resursa \"Practitioner\"",
}
],
},
{
},
{
],
},
{
],
}
}
]
}
}