Versions Compared

Old Version 8

changes.mady.by.user Sanofer Sameera S

Saved on

compared with

New Version Current

changes.mady.by.user Sanofer Sameera S

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Example of adding an Extension

Code Block
"IdentifierLookup":{
        "id": "org.bahmni.registration.identifier.your_identifier_id",
        "extensionPointId": "org.bahmni.registration.identifier",
        "type": "link",
        "src" : "/sample/index.html",
        "extensionParams": {
            "identifierType": [
                "sampleIdentifier1",
                "sampleIdentifier2"
            ],
            "nonEditable": ["givenName","middleName","familyName","gender","birthDate","age"],
            "linkDisplay": "Verify SampleIdentifier",
            "addressMap": {
                "city": "cityVillage",
                "state": "stateProvince",
                "postalCode": "postalCode",
                "line": ["address1"]
            }
            "requiredPrivilege": "app:registration"
        }

key

description

Mandatory

id

Unique identifier for extension

Y

extensionPointId

"org.bahmni.registration.identifier"

Y

type

link

Y

src

The source to be loaded on click of defined button

Y

extensionParams

Contains additional parameters mentioning the which include extra identifier’s name, which registration page feels become nonEditable after the Identifier linkage, what is the button name : linkDisplay, and address map that maps the address FHIR object (returned from the link to registration page) to field in registration pageand so on

Y

extensionParams.identifierType

one or more identifier type name. Note, if different identifier types require different source integration, define separate extensions.

Y

extensionParams.nonEditable

defines attributes which needs to be non-editable after extra Identifier linkage

N

extensionParams.linkDisplay

defines button display name

Y

extensionParams.addressMap

address map that maps the address FHIR object (returned from the link to registration page) to field in registration page

N

Assumptions

  1. The link specifies the path to the UI that needs to be rendered on click of the link identifier button.

  2. The external link returns an FHIR patient object to be mapped to Registration Page fields.

The returned payload is expected as a simple FHIR Patient resource.

Note: A complete patient resource is not required - only fields like identifier(s), name, birthdate, gender and address, those you want to be updated with a value from FHIR patient in registration page are expected.

If you provide patientUuid in FHIR patient .Id id field, it will redirect to that patientUuid dashboard and update the respective details passed as a part of FHIR object. If id not defined, it will redirect and update the details in the create new patient dashboard (new or edit patient) from where you opened extension iframe.

For example: consider the following FHIR Patient object

Code Block
{
  id: 'patientUuid',
  identifiers: [
    {
      type: {
        text: "identifierType1"
      },
      value: "hina@xyz"
    },
    {
      type: {
        text: "identifierType2"
      },
      value: "57-0517-6745"
    }
  ],
  names: [
    {
      familyName: 'Patel',
      givenName: [
        'Hina',
        ''
      ],
      use: ''
    }
  ],
  gender: "F",
  birthDate: "2000-10-21",
  isBirthDateEstimated: false
  contactPoint: [
    {
      system: 'phone',
      value: '+919800083232'
    }
  ],
  address: [
    {
      city: "",
      country: "IN",
      district: "Bhopal",
      line: [
        'A-12, Dholakpur'
      ],
      postalCode: "212021",
      state: "Madhya Pradesh",
      
    }
  ] 
}

...