http://snomed.info/sct
https://fhir.ee/CodeSystem/ads-adr-id
https://fhir.ee/CodeSystem/ads-oid
https://fhir.ee/CodeSystem/ametite-klassifikaator
https://fhir.ee/CodeSystem/date-accuracy-indicator
https://fhir.ee/CodeSystem/eriala
https://fhir.ee/sid/ehak
This fragment is not visible to the reader
This publication includes IP covered under the following statements.
Type | Reference | Content |
---|---|---|
web | akk.tehik.ee |
Identity of the terminology system
Binding: Isiku seos patsiendiga ![]() Fixed Value: http://snomed.info/sct |
web | www.hl7.ee |
IG © 2023+ HL7 Estonia
. Package ee.fhir.base#1.1.3 based on FHIR 5.0.0
. Generated 2025-06-19
Links: Table of Contents | QA Report |
web | geoportaal.maaamet.ee | NB! In case of an address, all fields provide informational content only, these fields may not be used for statistics or similar operations. The only exceptions that are strictly typed attributes: 1) country and 2) ADS extension . In case of an Estonian address, the ADS extension with values and services supported by Estonian Land Board is required. |
web | meteor.aihw.gov.au | In some circumstances, systems may capture date or dateTime data that has unknown or estimated parts. This coding indicates the accuracy of the day, month and year parts. This concept is equivalent to Australian Institute of Health and Welfare data element 294418 Date—accuracy indicator . |
web | akk.tehik.ee |
Unless not suitable, these codes SHALL be taken from
Isiku seos patsiendiga ![]() ( extensible to https://fhir.ee/ValueSet/isiku-seos-patsiendiga
)
|
web | term.tehik.ee | From https://term.tehik.ee/fhir |
web | akk.tehik.ee |
Identity of the terminology system Binding: Isiku seos patsiendiga ![]() Fixed Value: http://snomed.info/sct |
web | fhir.ee | HL7® FHIR® EE Base ja EE MPI juurutusjuhendite |
web | fhir.ee | HL7® FHIR® EE Base ja EE MPI juurutusjuhendite |
web | fhir.ee | siin |
web | fhir.ee | siin |
web | github.com | siin |
web | github.com | siin |
web | github.com | Esiteks vajate GitHubi kontot. Kui teil seda veel pole, minge GitHubi ja klõpsake paremas ülanurgas lingil „Sign up“ ja järgige sealt antud juhiseid. |
web | github.com | If you have any issue about Implementation Guide please create the Github ticket on the project site . |
web | github.com | You can download the source code of Implementation Guide from Github . Follow standard Pull request procedure to propose your changes. |
web | docs.github.com | You can download the source code of Implementation Guide from Github . Follow standard Pull request procedure to propose your changes. |
web | informatiestandaarden.nictiz.nl | FHIR resources tailored for local use, e.g. base profiles , whereas conformance requirements, must support flags and binding strengths have been held to as minimum as possible to support open-world modeling ; |
web | semver.org | Nationally defined FHIR profiles will be versioned during development using Git, following the standard GitFlow model. The versioning for published artefacts will broadly follow semantic versioning standards . The major and minor versions will be visible, and the patch version MAY also be exposed. Version numbers held in profiles and resource instanced MUST therefore be in one of the following forms: MAJOR – e.g. 1 MAJOR.MINOR – e.g. 1.0 MAJOR.MINOR.PATCH – e.g. 1.0.2 |
web | www.theserverside.com | Resource Name : The [ Base ], [ ResourceType ] and [ BusinessNames ] without hyphen (-) SHOULD be used as resource name. Segment names in FHIR Profile resource name MUST follow Pascal case convention . Resource name also known as computable name that MAY be used for code generation. |
web | www.theserverside.com | Resource Name : The [ Base ] and [ BusinessNames ] without hyphen (-) SHOULD be used as resource name. Segment names in FHIR operation name MUST follow Pascal case convention . Operation name also known as computable name that MAY be used for code generation. |
web | www.theserverside.com | Resource Name : [Base] and [BusinessNames] without hyphen (-) SHOULD be used as the resource name. Segment names in FHIR CodeSystem MUST follow Pascal case convention . |
web | fhir.ee | When using the FHIR Messaging Paradigm, messages will likely include references to external resources. These references SHOULD use an identifier from a known NamingSystem. This is known as a logical reference in the FHIR standard. The NamingSystem URI SHOULD be searchable on a FHIR Reference server to return the NamingSystem resource that describes the identifiers used (for example, https://fhir.ee/NamingSystem ). |
web | github.com | The Github repository for Estonian FHIR Base is https://github.com/HL7EE/ig-ee-base . |
web | github.com | Use https://github.com/HL7EE/ig-ee-base/issues for HL7EE EEBase issue mananagement. |
web | github.com | The new URI-s SHOULD be registred in GitHub fhir.ee project |
web | fhir.ee | All FHIR packages that may be used as dependecy for other packages SHOULD uploaded to Estonian FHIR Packages Repository through GitHub fhir.ee project . |
web | github.com | All FHIR packages that may be used as dependecy for other packages SHOULD uploaded to Estonian FHIR Packages Repository through GitHub fhir.ee project . |
tree-filter.png ![]() |