Universal API Implementation Guide
1.1.20 - ci-build

Universal API Implementation Guide - Local Development build (v1.1.20) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Technical Hints

Cleaning examples of meta and text tags

Use following regexp in VS.code to remove all meta tags from example resources:

."meta": \{\n.+\n.+\n.+\n\s+\},

Use following regexp in VS.code to remove all text tags from example resources:

."text": \{\n.+\n.+\n\s+\},

Matching Patient records on Genentech FHIR server

Records in the incoming bundles are processed in the context of Organization. Organization is identified using "official" identifier in Organization resource for Organization with type.code = "prov". This identifier is auto generated by Genentech middle-tier layer and is a concatenation of "Vendor System Identifier" from MessageHeader.source.name with identifier on Organization submitted by the sender.

Identifier in the Organization resource submitted by the sender example:

"identifier": [{
           "assigner": {
             "display": "Vendor One Name"
           },
           "system": "http://nema.org/examples/organizations",
           "use": "usual",
           "value": "HOSP-12345"
         }

Resulting in "official" identifier which is part of the uapi-as-bundle-after</a>

        {
           "assigner": {
             "display": "UAPI Experience API Mulesoft"
           },
           "system": "http://dev.gene.com/fhir/mulesoft",
           "use": "official",
           "value": "Vendor1_HOSP-12345"
        }

How to use fhir_validator.jar to validate test bundles against UAPI FHIR Profiles

TBD… //TODO: populate content here…

Sample .NET client implementation calling /enrollment endpoint

TBD … //TODO: populate content here…

Sample Node.js client implementation calling /enrollment endpoint

TBD … //TODO: populate content here…