HL7 FHIR® Implementation Guide: Electronic Case Reporting (eCR) - US Realm
1.1.0 - STU 2 Ballot

This page is part of the electronic Case Reporting (eCR) (v1.1.0: STU 2 on FHIR R4 Ballot 1) based on FHIR R4. The current version which supercedes this version is 2.1.0. For a full list of available versions, see the Directory of published versions

Resource Profile: RR_Rules_Authoring_Agency_Organization - Mappings

Mappings for the rr-rules-authoring-agency-organization resource profile.

Mappings for RR Rules Authoring Agency Organization mapping to CDA ()

This table maps RR Rules Authoring Agency profile to CDA

RR_Rules_Authoring_Agency_Organization
Organization
   textReportability Response Coded Information Organizer/Relevant Reportable Condition Observation/Reportability Information Organizer/Rules Authoring Agency/participantRole/playingEntity/desc
   identifierReportability Response Coded Information Organizer/Relevant Reportable Condition Observation/Reportability Information Organizer/Rules Authoring Agency/participantRole/id
   nameClinicalDocument/componentOf/encompassingEncounter/responsibleParty/assignedEntity/representedOrganization/name, Reportability Response Coded Information Organizer/Relevant Reportable Condition Observation/Reportability Information Organizer/Rules Authoring Agency/participantRole/playingEntity/name
   telecomReportability Response Coded Information Organizer/Relevant Reportable Condition Observation/Reportability Information Organizer/Rules Authoring Agency/participantRole/telecom
   addressReportability Response Coded Information Organizer/Relevant Reportable Condition Observation/Reportability Information Organizer/Rules Authoring Agency/participantRole/addr

Mappings for eICR Organization name mapping to CDA ()

This table maps eICR and RR Organization profile to CDA

RR_Rules_Authoring_Agency_Organization
Organization
   textReportability Response Coded Information Organizer/Relevant Reportable Condition Observation/Reportability Information Organizer/Rules Authoring Agency/participantRole/playingEntity/desc
   identifierReportability Response Coded Information Organizer/Relevant Reportable Condition Observation/Reportability Information Organizer/Rules Authoring Agency/participantRole/id
   nameClinicalDocument/componentOf/encompassingEncounter/responsibleParty/assignedEntity/representedOrganization/name, Reportability Response Coded Information Organizer/Relevant Reportable Condition Observation/Reportability Information Organizer/Rules Authoring Agency/participantRole/playingEntity/name
   telecomReportability Response Coded Information Organizer/Relevant Reportable Condition Observation/Reportability Information Organizer/Rules Authoring Agency/participantRole/telecom
   addressReportability Response Coded Information Organizer/Relevant Reportable Condition Observation/Reportability Information Organizer/Rules Authoring Agency/participantRole/addr

Mappings for ServD (http://www.omg.org/spec/ServD/1.0/)

RR_Rules_Authoring_Agency_Organization
OrganizationOrganization
   identifier./Identifiers, n/a
   identifier (NPI)./Identifiers, n/a
   identifier (CLIA)./Identifiers, n/a
   active./Status (however this concept in ServD more covers why the organization is active or not, could be delisted, deregistered, not operational yet) this could alternatively be derived from ./StartDate and ./EndDate and given a context date.
   typen/a
   name.PreferredName/Name, ./PrimaryAddress and ./OtherAddresses
   telecom./ContactPoints
   address./PrimaryAddress and ./OtherAddresses, n/a
      use./AddressPurpose
      line./StreetAddress (newline delimitted)
      city./Jurisdiction
      state./Region, ./Sites
      postalCode./PostalIdentificationCode
      country./Country
      period./StartDate and ./EndDate
   partOfn/a

Mappings for HL7 v2 Mapping (http://hl7.org/v2)

RR_Rules_Authoring_Agency_Organization
Organization(also see master files messages)
   identifierXON.10 / XON.3
   identifier (NPI)XON.10 / XON.3
   identifier (CLIA)XON.10 / XON.3
   activeNo equivalent in HL7 v2
   typeNo equivalent in v2
   nameXON.1
   telecomORC-22?
   addressORC-23?
      useXAD.7
      typeXAD.18
      textXAD.1 + XAD.2 + XAD.3 + XAD.4 + XAD.5 + XAD.6
      lineXAD.1 + XAD.2 (note: XAD.1 and XAD.2 have different meanings for a company address than for a person address)
      cityXAD.3
      districtXAD.9
      stateXAD.4
      postalCodeXAD.5
      countryXAD.6
      periodXAD.12 / XAD.13 + XAD.14
   partOfNo equivalent in HL7 v2
   contact
      namePID-5, PID-9
      telecomPID-13, PID-14
      addressPID-11

Mappings for RIM Mapping (http://hl7.org/v3)

RR_Rules_Authoring_Agency_Organization
OrganizationEntity. Role, or Act, Organization(classCode=ORG, determinerCode=INST)
   textAct.text?
   containedN/A
   extensionN/A
   modifierExtensionN/A
   identifier.scopes[Role](classCode=IDENT)
   identifier (NPI).scopes[Role](classCode=IDENT)
   identifier (CLIA).scopes[Role](classCode=IDENT)
   active.status
   type.code
   name.name
   alias.name
   telecom.telecom
   address.address
      idn/a
      extensionn/a
      useunique(./use)
      typeunique(./use)
      text./formatted
      lineAD.part[parttype = AL]
      cityAD.part[parttype = CTY]
      districtAD.part[parttype = CNT | CPA]
      stateAD.part[parttype = STA]
      postalCodeAD.part[parttype = ZIP]
      countryAD.part[parttype = CNT]
      period./usablePeriod[type="IVL<TS>"]
   partOf.playedBy[classCode=Part].scoper
   contact.contactParty
      idn/a
      extensionn/a
      modifierExtensionN/A
      purpose./type
      name./name
      telecom./telecom
      address./addr
   endpointn/a

Mappings for FiveWs Pattern Mapping (http://hl7.org/fhir/fivews)

RR_Rules_Authoring_Agency_Organization
Organization
   identifierFiveWs.identifier
   identifier (NPI)FiveWs.identifier
   identifier (CLIA)FiveWs.identifier
   activeFiveWs.status
   typeFiveWs.class