Optional URL Parameters

When you define in Portal Builder an "External Page" tab, the URL you set there can be dynamic. BioT enables you to embed dynamic parameters within the URLs specified for "External Page" tabs.

Specifying parameters

To include dynamic parameters within URLs, enclose them within double curly braces {{parameter_name}}.

For example:


BioT will attempt to resolve these parameters against the relevant context entity.
If resolution is not possible, BioT will pass 'blank' instead of the parameter value.

3 parameters: User, Entity & Entity Type

JSON NameDescriptionComment
userData about the current logged in userAlways exists
entityTypeDescribes the type of entity to expect under the entity attribute.Only exists when the iFrame is embedded under another entity
entityData about the current entity on screen.Only exists when the iFrame is embedded under another entity

Accessing user attributes

For any view in any of BioT's portals, the following user attributes are available:

  • _accessToken
  • _refreshToken
  • _id
  • _userType
  • _ownerOrganizationId
  • _templateName

Accessing entity attributes

Context passed from expanded views (views ending in "Add, Edit, Expand" in Portal Builder) includes an additional variable, "entity," along with all its attributes.


Note that the resolved parameters names are case sensitive.


Opening a custom tab in the main window will send the embedded iFrame the following object:

   "user": {

While opening a custom tab in a patient entity will send the embedded iFrame the following object:

   "user": {
      "_email":"[email protected]",

In the latter case, if we would like to set the following parameters as query parameters:

  • The current entity type
  • Entity first name
  • Entity last name
  • Logged in user template name

We can access them like this:

Current entity type: {{entityType}}
First name: {{entity._name.firstName}}
Last name: {{entity._name.lastName}}
Logged in user template name: {{user._templateName}}

And a possible URL construction would be:

Finally BioT will initiate an HTTPS request to:

GET https://example.com?eType=patient&fName=Patient&lName=Zero&template=Clinician

Nested entities

BioT's functionality does not extend to the resolution of nested entities. This means that attributes residing within entities linked to the context entity, such as a device entity referenced by a patient entity, cannot be directly accessed.