Question: translating v2 to FHIR

Dec 18, 2013

Questions

  1. the proper way of converting XCN segment data into FHIR Practitioner resource (to fill encounter.participants) is unclear.
  2. I can’t find neither the proper segment nor the way of creating FHIR Location resource (to fill encounter.locations) and FHIR Organization resource (to fill encounter.service_provider).
  3. I would like to know if there are mappings from v2 value set 0112 to FHIR value set encounter-discharge- disposition and from v2 value set 0023 to FHIR value set encounter-admit-source. If I’m not mistaken, these mappings are required to fill encounter.hospitalization. discharge_disposition and encounter.hospitalization. admit_source.

Answers

  1. XCN - this table summarises the mappings from XCN to practitioner:
1 Person Identifier Practitioner.identifier.value
2 Family Name Practitioner.name.family
3 Given Name Practitioner.name.given
4 Second and Further Given Names or Initials Thereof Practitioner.name.given (see notes about name parts athttp://hl7.org/implement/standards/fhir/datatypes-examples.html#humanname)
5 Suffix (e.g., JR or III) Practitioner.name.suffix
6 Prefix (e.g., DR) Practitioner.name.prefix
7 Degree (e.g., MD) Practitioner.qualification.code
8 Source Table No equivalent in FHIR (e.g. extension if really necessary)
9 Assigning Authority Practitioner.identifier.system and/or Practitioner.name.assigner
10 Name Type Code Practitioner.name.use
11 Identifier Check Digit No equivalent in FHIR (e.g. extension if really necessary)
12 Check Digit Scheme No equivalent in FHIR (e.g. extension if really necessary)
13 Identifier Type Code Practitioner.identifier.value
14 Assigning Facility Maybe Practitioner.identifier.assigner
15 Name Representation Code Helps to build Practitioner.name.text
17 Name Validity Range Practitioner.identifier.period
18 Name Assembly Order Helps to build Practitioner.name.text
19 Effective Date Practitioner.identifier.period
20 Expiration Date Practitioner.identifier.period
21 Professional Suffix Practitioner.qualification.code
22 Assigning Jurisdiction Practitioner.qualification.issuer
23 Assigning Agency or Department Practitioner.qualification.issuer
24 Security Check No equivalent in FHIR (e.g. extension if really necessary)
25 Security Check Scheme No equivalent in FHIR (e.g. extension if really necessary)

There’s nothing in practitioner that’s mandatory that’s not in this table (actually, nothing is mandatory anyway). Note that the v2 mapping table for practitioner takes a different approach.

What this table doesn’t address is the url used to identify the practitioner. This has to be synthesized from a repository of practitioners. In some circumstances, you might be able to construct the URL purely from XCN.1, but you couldn’t take this generally for granted.

  1. Encounter.location. According to the existing mappings: PV1-3-assigned patient location / PV1-6-prior patient location / PV1-11-temporary location / PV1-42-pending location / PV1-43-prior temporary location, and for the service provider: PV1-10-hospital service / PL.6 Person Location Type & PL.1 Point of Care (though see the notes in the mapping)

3a. v2 tables 0023 and 0112 are place holders for locally defined codes (in FHIR parlance, a terminology binding with just a description, no reference). So there’s no way to provide general mappings