Thank you for the samples. Now it works fine and I get JWT. I have seen this parameters in some other post in community. What is the exact use of these parameters dispatcher class.

 Parameter TokenLoginEndpoint = "login"; Parameter TokenLogoutEndpoint = "logout"; Parameter TokenRevokeEndpoint = "revoke"; Parameter TokenRefreshEndpoint = "refresh";

Yes. my web application is /api and invoked this http://localhost:52774/api/login

Hello @Luis Angel Pérez Ramos 

I've enabled and configured JWT in my Web application. I'm trying to call the /login method from post man with body of contents  {"user":"{YOURUSER}", "password":"{YOURPASSWORD}"} but I got 404 not found error. Did I anything missed/required.

As you mentioned 

With this configuration we will not need anything else to start using this authentication mode in our web applications.

However This is for clarification

Do I need to write a custom login method or existing is enough? 

Do I need to include  /login, /logout etc.. endpoints in urlmap?

Hello @Yone Moreno 
Just a thought. Convert the HL7 message into SDA. Create a clone class like SDA with extends of Ens.Request. Create a instance of the class and import the String into the object and finally store it like below.

ClassMethod HL7ToCustomEnsReq()
{
    #dim xml As %Stream.GlobalCharacter
    set hl7 = ##class(EnsLib.HL7.Message).%New()
    
    set tSC = ##class(HS.Gateway.HL7.HL7ToSDA3).GetSDA(hl7,.xml)
    $$$ThrowOnError(tSC)
    
    set reqObj = ##class(Mensajes.Request.ConsentimientoInformado.HUC.ORUHL725OutRequest).%New()
    do reqObj.XMLImportSDAString(xml.Read())
    set tSC = reqObj.%Save()
    $$$ThrowOnError(tSC)
}

Thanks you @Guillaume Rongier !

Hopefully this will be helpful

As per the documentation The I had raised the same question Currently, InterSystems products do not provide the ability to validate a resource against a profile. Validation is limited to the base FHIR specification.

Thanks @Luis Angel Pérez Ramos for pointing the documentation

As for As I see there is no option to export the Business partners along with production export. Even there is no option with with deployable settings and config.Item definition as well. The Business partner details are stored in Ens. Config.BusinessPartner.

So, I hope you need to manually export your global's and import in to the another instance. 

Basically %JSONExport()  API method only works if you're class definition extends with %JSON.Adaptor. class You can even use the below to write your JSON response in UI

do ##Class(%REST.Impl).%WriteResponse(response)

hello @Yone Moreno 

You don't need to include the query params in the Url. That's is basically available in %request CSP object. You can take the query parameter values like below. And :studies represents it's a dynamic URL parameter value.

XData UrlMap [ XMLNamespace = "http://www.intersystems.com/urlmap" ]
{
<Routes>
<Route Url="/:studies" Method="GET" Call="consultarEstudiosDatosPaciente"/>
</Routes>
}

ClassMethod consultarEstudiosDatosPaciente(studies As %String="") As %Status
{
    
    set patientId = %request.Get("patientId")
    /// or 
    set patientId = %request.Data("patientId", 1)
    return $$$OK
}

Thanks you all!

Hello @Colin Brough 

I Believe, There is no functional difference between rule 1 and rule 2 except the invoking the DTL twice and finally call the Target. By default it has the feature to call multiple targets once the transformation completed. You utilized the feature in rule 2. That's the exact way to call multiple target unless different message and different transformation required. There will be a performance difference should be there. Because it executes the DTL first every time and eventually call the targets asynchronously(Whether it's asynchronous or synchronous It depends on the configuration in production Business process).

xData block data's are basically stored the as a stream object in the class definition. If this is a property oriented then create a stream property  %Stream.GlobalCharacter and store the values.