FHIR © HL7.org  |  FHIRsmith 4.0.1  |  Server Home  |  XIG Home  |  XIG Stats  | 

FHIR IG analytics

Packagehl7.fhir.uv.omop
Resource TypeActorDefinition
IdActorDefinition-imp.json
FHIR VersionR5
Sourcehttps://build.fhir.org/ig/HL7/fhir-omop-ig/ActorDefinition-imp.html
URLhttp://hl7.org/fhir/uv/omop/ActorDefinition/imp
Version2.0.0-ballot
Statusactive
Date2026-07-31
NameETL_Implementer
TitleETL Implementer
Realmuv
Authorityhl7
DescriptionThe organization or team that designs, deploys, configures, and operates a FHIR-to-OMOP transformation. The Implementer makes choices that cannot be made by software alone: which use cases the OMOP instance supports, which identifier-handling strategies apply, what filtering rules are consistent with the research purpose, and what the legal basis for data access is. Many of the most important conformance statements in this guide attach to the Implementer because they require human judgment, documentation, or governance activity rather than runtime behavior. Distinguishing the Implementer as a formal actor is what allows this guide to carry conformance statements about ETL documentation, privacy assessment, and governance, statements that would be awkward to attach to a software component.
Typeperson

Resources that use this resource

No resources found


Resources that this resource uses

No resources found


Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ActorDefinition imp

Actor: ETL_Implementer ETL ImplementerType: person

Source1

{
  "resourceType": "ActorDefinition",
  "id": "imp",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "brr"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 2,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/omop/ImplementationGuide/hl7.fhir.uv.omop"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/omop/ImplementationGuide/hl7.fhir.uv.omop"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/omop/ActorDefinition/imp",
  "identifier": [
    {
      "system": "urn:ietf:rfc:3986",
      "value": "urn:oid:2.16.840.1.113883.4.642.40.77.12.1"
    }
  ],
  "version": "2.0.0-ballot",
  "name": "ETL_Implementer",
  "title": "ETL Implementer",
  "status": "active",
  "experimental": false,
  "date": "2026-07-31",
  "publisher": "HL7 International / Biomedical Research and Regulation",
  "contact": [
    {
      "name": "HL7 International / Biomedical Research and Regulation",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/rcrim"
        }
      ]
    }
  ],
  "description": "The organization or team that designs, deploys, configures, and operates a FHIR-to-OMOP transformation. The Implementer makes choices that cannot be made by software alone: which use cases the OMOP instance supports, which identifier-handling strategies apply, what filtering rules are consistent with the research purpose, and what the legal basis for data access is. Many of the most important conformance statements in this guide attach to the Implementer because they require human judgment, documentation, or governance activity rather than runtime behavior.\n\nDistinguishing the Implementer as a formal actor is what allows this guide to carry conformance statements about ETL documentation, privacy assessment, and governance, statements that would be awkward to attach to a software component.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "type": "person"
}